Is Payload Validation in em mandatory?

SOA 11.1.1.3
Is Payload Validation in EM, mandatory to select? if Yes, can anyone tell me why ?
If I select , and when source system invokes my bpel wsdl, Error: "Schema validation failed for message part payload. Please ensure at the message sender level that the data sent is schema compliant.”
If I don't select it works fine. Can I proceed this way?
Thanks
Edited by: user13326981 on Nov 24, 2010 2:56 PM

Hi,
No its not mandatory. In case if you need to validate your payload you might have to select this.
Regards,
Ramesh

Similar Messages

B2B-51507- Payload validation error - 11.1.1.7 Latest Version

Anuj/Nitesh (B2B Gurus)
I am facing a problem when Posting the message from SOA to B2b (XML->EDI) using the B2b Adapter.
Flow is : Ebusiness->PLSQL->AQ->BPEL->B2B. Once the message is posted to B2b It is throwing the following Error.
But I am passing all the mandatory and Optional Parameters.
Tried the Following Threads, But No luck. I am passing all the Mandatory Parameters.
How to map Internal-Properties in XSLT.
Oracle B2B Payload Validation exception
Scenario - 1 (Success No Errors , Output Does not Contain PO Details)
Disabled the Validate flag in the Partner Agreement for the B2B Document.
Verified the B2b Wired Message, Output got generated but without the PO information I am passing from BPEL.
Scenario - 2 (Error )
Enabled the Validate flag in the Partner Agreement for the B2B Document. The system is generating an error and throwing list of errors.
Error
Id
C064016C14103689486000005559CD14
Message Id
C064016C14103688C7F000005559CD0F
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
ABC
Receiver Type
Name
Receiver Value
TEST123
Sender
ABC
Receiver
TEST123
Agreement Id
EDI_850_tpa_Lt7763342564515893374
Agreement
XXX_EDI_X12_4010_850_Outbound
Document Type
850
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
9/9/2013 10:48
Receive Time Stamp
9/9/2013 10:48
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
5471
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Sep 05 11:51:44 CDT 2013 - 4
Collaboration Id
C064016C14103688E1A000005559CD13
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : Error reporting limit exceeded. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A functional group code mismatch was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A transaction ID mismatch was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered.
Error Brief :^M
Error reporting limit exceeded.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Description: Payload validation error., null, null, null, null, C064016C140EF31BFCA000005559CC
A4, null, null, 1258, B2B-51507, null, null, null, null, null, 2013-09-05 12:35:49.092, null, ^M
Error :^M
Analysis halted after 101 error(s) (Limit for Transaction is 100). Large numbers of errors usually indicate that the same error is repeatedly encountered in multiple segments or transactions. Fix the repeating error and resubmit the test to obtain further results.^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 1{br}{tab}Characters: 210 through 212^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 2{br}{tab}Characters: 247 through 257^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 3{br}{tab}Characters: 292 through 294^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 4{br}{tab}Characters: 329 through 339^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 5{br}{tab}Characters: 374 through 376^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 6{br}{tab}Characters: 411 through 426^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 7{br}{tab}Characters: 463 through 465^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 8{br}{tab}Characters: 502 through 517^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 9{br}{tab}Characters: 552 through 558^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 10{br}{tab}Characters: 593 through 597^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 11{br}{tab}Characters: 632 through 633^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 12{br}{tab}Characters: 668 through 673^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 13{br}{tab}Characters: 708 through 717^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 14{br}{tab}Characters: 752 through 753^M
Thanks
Rao.

Issue is resolved by doing the Following Steps.
1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
2. Export the XSD and refer it in the BPEL process and do the transformation.
Thanks
Nethi.

B2B-51507 - Payload Validation Error - while creating VDA -4913V3

I created a document definition under Positional Flat file for VDA-> 4913V4. I created ecs file using the Document editor and created the xsd. I used both these files in creating the Document definition. In the document definition, under identification tab, I have these values.
Identification Value -> empty
Identification Start Position -> 0
Identification End Position -> 128
And I created a Partner Agreement using this Document Definition. I created a channel to send the document to GXS Mailbox.
In the agreement if I have both Validate and Translate checked on, I am getting an error which is show in the reports->Business Message.
Error Code B2B-51507
Error Description Machine Info: (RRDV2SOA) Description: Payload validation error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Payload validation error.
If I have only Translate checked on, I am not getting any error, but the message that is sent to GXS is zero bytes.
If I leave both Validate and translate unchecked, the xml is sent to GXS but not the native Format.
I took the payload from the business message and validated and it looks correct.
I am using the sample data that is already validated in the B2B Document Editor using Data Analyzer.
Can you help me on this. I am not sure what I am doing wrong. If needed I can send you the ecs, xsd, and B2B partner definition export zip file to your email address.
Here is the logfile for this error.
[2011-04-06T21:00:41.652-07:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1a33f088] [userId: <anonymous>] [ecid: 0000Iwi7c0MCcpiF_7I7S61DVcAD0051W4,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [dcid: 4e45f5dff566a29f:-335a9823:12eb62ea520:-7ffd-000000000000008c] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
[2011-04-06T21:00:41.653-07:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1a33f088] [userId: <anonymous>] [ecid: 0000Iwi7c0MCcpiF_7I7S61DVcAD0051W4,0] [APP: soa-infra] [dcid: 4e45f5dff566a29f:-335a9823:12eb62ea520:-7ffd-000000000000008c] Error -: B2B-51507: Payload validation error.: Error -: B2B-51507: Payload validation error.[[
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:835)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
... 11 more
Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-51507: Payload validation error.: Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:835)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
... 11 more
Thank you
Krishna.

I selected the option "Save guideline before exporting". I am guessing it is failing on the main element of the xml message because of some namespace issue. I am generating the XML using xsl transformationin BPEL and sending the XML payload to B2B Service.
Is there a way to know what part of the XML is erroring duing the validation on the server. The error message is not helpful even I turned on Trace 32 level.
Any ideas?
Thank you
Krishna

Payload validation Error - Outbound flow

Hi,
I am trying to create an outbound flow to send a X12,4010,810 document to a trading partner.
Got the error - Payload Validation error.
Payload is as below
<?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
Can someone suggest what is the problem with this payload.

More detail --
Below is the message that is displayed in Oracle B2B Reports -> Business Message
Id
7F000001144BE0AB3A100000231A6860
Message Id
11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
OracleServices
Receiver Type
Name
Receiver Value
MarketInc
Sender
OracleServices
Receiver
MarketInc
Agreement Id
OS_MI_X12_4010_810_OutboundInvoiceAgr
Agreement
OS_MI_X12_4010_810_OutboundInvoiceAgr
Document Type
IN
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
Mar 13, 2014 7:42 PM
Receive Time Stamp
Mar 13, 2014 7:42 PM
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
2344
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Mar 17 08:30:33 CDT 2014 - 8
Collaboration Id
7F000001144BE0AB37E00000231A6850
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Machine Info: (XXXX) Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : XEngine error.
Application Message :
Id7F000001144BE0AB22400000231A6820Sender Id TypeSender ValueOracleServicesReceiver Id TypeReceiver ValueMarketIncDocument TypeINDocument Definition810_DefDocument Protocol NameEDI_X12Document Protocol Version4010Refer To Application Message IdRefer To Application Message IdApp Conversation IdApp Message property{fabric.enterpriseId=-1, b2b.documentProtocolVersion=4010, b2b.documentDefinitionName=810_Def, b2b.messageId=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, MESH_METRICS=null, b2b.messageType=1, tracking.parentReferenceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E:954F6910AB1111E3BF8A5F99BC4D6B4E:oneway, tracking.compositeInstanceId=20012, tracking.ecid=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, b2b.toTradingPartnerId=MarketInc, b2b.fromTradingPartnerId=OracleServices, tracking.compositeInstanceCreatedTime=Thu Mar 13 19:42:55 CDT 2014, tracking.conversationId=snbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4., tracking.parentComponentInstanceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E, b2b.documentTypeName=IN}DirectionOUTBOUNDStateMSG_COMPLETEError CodeError TextError DescriptionCreatedMar 13, 2014 7:42 PMModifiedMar 13, 2014 7:42 PMMessage Size2344PayloadPayloadBusiness MessageBusiness MessageRetry Interval0Reattempt CountRemaining Retry0ECID11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfcComposite Instance Id20012Parent Composite Instance Idmediator:954F1AF0AB1111E3BF8A5F99BC4D6B4EConversation IdsnbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4.Domain NamedefaultComposite NameOSToMIOutboundInvoiceProjectComposite Version1.0Reference NameB2BOSToMarketIncOutboundUrl
Payload Storage :
<?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
I have set the following b2b headers in SOA before sending it to B2B outbound
Constant: 4010_810_Def Property: b2b.documentDefinitionName
Constant: 4010 Property: b2b.documentProtocolVersion
Constant: OracleServices Property: b2b.fromTradingPartnerId
Constant: MarketInc Property: b2b.toTradingPartnerId
Constant: 1 Property: b2b.messageType
Constant: IN Property: b2b.documentTypeName ( I defined my docuemnt with name 'IN')
Property: tracking.ecid Property: b2b.messageId

Payload Validation failing for EBM

Hi,
I have a composite which takes input based on a simple XSD.
Inside the composite the input is mapped to Sales Order EBM and this EBM is sent as input to other composite.
For data validation purpose, I switched on Payload Validation for this composite in Weblogic EM.
The input data validation works fine but it's throwing follwing error while invoking composite which accepts EBM as input.
<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>oracle.fabric.common.FabricInvocationException: Schema validation failed for message part payload. Please ensure at the message sender level that the data sent is schema compliant.</summary>
</part>
<part name="detail">
<detail>Element 'ProcessSalesOrderFulfillment' not expected.</detail>
</part>
<part name="code">
<code>null</code>
</part>
</remoteFault>
</bpelFault>
</fault>
The payload validation error is occuring for all composites which accepts EBM as input. It picks the attribute name just after the header and says element not expected.
Any help is greatly appreciated.
Thanks,
Ravi

Please ensure that you have created EBS properly, verify all the datatypes of the elements in input XSD & EBO schema. And also verify whether EBM header is reflecting properly.
One more thing you should able to navigate from EBS to EBM, EBM to EBO then only you can assume you have done all things correctly. If not reconstruct EBS, EBM & EBO with valid request & response messages.

Oracle B2B Payload Validation exception

Hi,
I'm trying to input EDI and get XML as output, the EDI file gets picked up, a note, these files are all generated in the Document Editor, it's the X12 4010, 850 example. It picks up my EDI and if Translate is turned off, it validates against the ECS file and dumps the EDI file into the output partner's folder. If I turn translate on though, I get a validation error, I did tick save before generating the XSD, no validation errors in document editor. Please advise.... also note that I am doing this on the SOA VM as supplied on the Oracle website.
Id    7F00000113F80756FB800000A2DAF570
Message Id    1
Refer To Message    Refer To Message
Sender Type    Name
Sender Value    MyCompany
Receiver Type    Name
Receiver Value    TheirCompany
Sender    MyCompany
Receiver    TheirCompany
Agreement Id    New Agreement_0624_0749
Agreement    New Agreement_0624_0749
Document Type    850
Document Protocol    EDI_X12
Document Version    4010
Message Type    REQ
Direction    OUTBOUND
State    MSG_ERROR
Acknowledgement Mode    NONE
Response Mode    NONE
Send Time Stamp    06/26/2013 05:29:06 AM
Receive Time Stamp    06/26/2013 05:29:06 AM
Document Retry Interval(Channel)    0
Document Remaining Retry(Channel)    0
Document Retry Interval(Agreement)    0
Document Remaining Retry(Agreement)    0
Native Message Size
Translated Message Size    4260
Business Action Name
Business Transaction Name
Xpath Name1    XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2    XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3    XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name    CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name    CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message    Wire Message
Application Message    Application Message
Payload Storage    Payload Storage
Attachment    Attachment
Label    soa_b2b_ - Wed Jun 26 01:15:31 PDT 2013 - 2
Collaboration Id    7F00000113F80756AE600000A2DAF560
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name    Generic File
Exchange Protocol Version    1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code    B2B-51507
Error Description    Machine Info: (soabpm-vm) Description: Payload validation error.
Error Level    ERROR_LEVEL_COLLABORATION
Error Severity    ERROR
Error Text    Error Brief : XML Parser error.
<Jun 26, 2013 4:09:26 AM PDT> <Error> <oracle.soa.b2b.engine> <BEA-000000> <Error -: B2B-51507: Payload validation error.
        at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
        at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
        at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-51507: Payload validation error.
        at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
        at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
        at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>
<Jun 26, 2013 5:29:07 AM PDT> <Error> <oracle.soa.b2b.engine> <BEA-000000> <Error -: B2B-51507: Payload validation error.
        at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
        at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
        at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-51507: Payload validation error.
        at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
        at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
        at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
        at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>

Issue is resolved by doing the Following Steps.
1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
2. Export the XSD and refer it in the BPEL process and do the transformation.
Thanks
Nethi.

Doubt in XML payload validation in PI 7.1

Dear All,
I understand that the PI message payload can be validated against a XSD/XML structure..
but i do not understand its advantage as the payload will by default be validated against our source data type..
then why do we need it to get validated against some other xml at adapter/IE level

Dear Ravi,
A very good question asked by you... Actually to tell there is not much of an advantage...
What it actually does is..
1)XML Validation allows you to check the structure of a PI message payload. The structure check is
performed using saved data types.
2)Syntax validation of the incoming message payload is done at the Advanced Adapter Engine and at
the Integration Engine against their XML Schema stored in the File System.
3)Syntax validation of outgoing message payload is done at the Integration Engine against their XML
Schema stored in the File System.
And regarding your question why do we need it ..." This feature is demanded by the customers. "
Source:https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406a97c4-748c-2a10-f2be-cb63c5b0a11f
Rgds
joel

T-code:FB60 and MIRO business place validation Section Code mandatory

Hi,
My requirement is to make mandatory in MIRO and FB60 field: BUPLA-business place and field:SECCO-Section Code.
I have done validation through GGB0 . i am facing problem
prerequisite: syst-tcode = 'FB60'
check bseg-bupla   <>   ' ' and bseg-secco <> ' '
message 'Enter business place and business section.
This is working fine when bseg-bupla and bseg-secco is not entered .
but when user enter value in both fields bseg-bupla and bseg-secco .
in table bseg-bupla and bseg-secco both become blank.
Is ther any other method to achieve this
regads,
K.Shobha.

Hi
Have you tried it with customizing tools? I understand that you can achieve it. I think that you want to populate these fields if you have a field status group for this account (check it in FS00). You can create a field status group for this account and do mandatory this fields. If you have doubts, search the help of a FI consultant.
If you see the help for this field:
Field status group
    Determines the screen layout for document entry.
    Fields can have the following statuses:
    o   Optional entry - you can enter data in the field
    o   Mandatory entry - you must enter data in the field
    o   Suppressed - the field does not appear on the screen
You can mantain it with tcode OBC4.
I hope this helps you.
Regards
Eduardo

OSB: Payload validation required for empty elements inside OSB process.

Hello
I need to validate the payload for non-empty elements. If the payload is completely empty then OSB should throw an error that the submitted payload is empty.
If the payload contains at least one element then it should pass through.
As in process to test this particular one, i have tried with the following code to generally validate for an element.
xquery version "1.0" encoding "Cp1252";
(:: pragma bea:global-element-parameter parameter="$inputParameters1" element="ns0:InputParameters" location="../adapter/StoreProcDB/xsd/StoreProcDBService_sp.xsd" ::)
(:: pragma bea:schema-type-return type="ns1:Validation" location="../xsd/validation.xsd" ::)
declare namespace xf = "http://tempuri.org/StoreProc_osb/transformation/PayloadValidation/";
declare namespace ns1 = "http://www.sigmainfo.com/validation";
declare namespace ns0 = "http://xmlns.oracle.com/pcbpel/adapter/db/sp/StoreProcDBService";
declare function xf:PayloadValidation($inputParameters1 as element(ns0:InputParameters))
as element()
<ns1:Validation>
          <ns1:Payload>{$inputParameters1/.}</ns1:Payload>
          <ns1:ValidationErrorList>
               (: BEGIN - Required Field Validations :)
          (:     if (empty($inputParameters1/ns0:ACCOUNTNUMBER/text())) then
                    <ns1:ValidationError>
                         <ns1:code>1</ns1:code>
                         <ns1:message>ACCOUNTNUMBER: Required Field</ns1:message>
                    </ns1:ValidationError> :)
               if (empty($inputParameters1/ns0:AUDITUSER/text())) then
                    <ns1:ValidationError>
                         <ns1:code>1</ns1:code>
                         <ns1:message>AUDITUSER: Required Field</ns1:message>
                    </ns1:ValidationError>
               else ''
               (: END - Required Field Validations :)
</ns1:ValidationErrorList>
     </ns1:Validation>
declare variable $inputParameters1 as element(ns0:InputParameters) external;
xf:PayloadValidation($inputParameters1)
But it throws the following error:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
REQUEST DOCUMENT:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soapenv:Body>
<stor:InputParameters
xmlns:stor="http://xmlns.oracle.com/pcbpel/adapter/db/sp/StoreProcDBService">

<stor:P_ACCOUNTNUMBER>00101</stor:P_ACCOUNTNUMBER>

<stor:P_AUDITUSER>venkat</stor:P_AUDITUSER>
</stor:InputParameters>
</soapenv:Body>
</soapenv:Envelope>
RESPONSE DOCUMENT:
The invocation resulted in an error: . <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-382505: OSB Validate action failed validation</faultstring><detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382505</con:errorCode>
<con:reason>OSB Validate action failed validation</con:reason>
<con:details>
<con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:message>
Incompatible elements: expected an XML instance of name "{http://xmlns.oracle.com/pcbpel/adapter/db/sp/StoreProcDBService}InputParameters", but found an XML instance of name "{http://schemas.xmlsoap.org/soap/envelope/}Body".
</con1:message>
<con1:xmlLocation/>
</con1:ValidationFailureDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>stage1</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
But this is not the way it should be done as i progress.
Please suggest a simple way to have a pragma with sample and complete validation for the input payload.
Appreciate your help in advance
Regards
Venkat

Venkat,
Find below url's for implementing security policies in OSB
http://docs.oracle.com/cd/E17904_01/doc.1111/e15866/owsm.htm#CHDEEGJI
http://docs.oracle.com/cd/E17904_01/doc.1111/e15866/owsm.htm#CHDBIJHD
http://niallcblogs.blogspot.in/2010/07/osb-11g-and-wsm.html
http://biemond.blogspot.in/2009/06/ws-security-in-osb.html
Regards,
Abhinav

B2B-51507 Payload validation error

Can someone tell me a what point in the b2b inbound process MDN errors are sent.
I assumed (I know shouldn't assume anything in this game) that with translate and validate on an agreement that an MDN would be sent if translate or validation fails, but this does not seem to be the case. I am using 11G.
John

I selected the option "Save guideline before exporting". I am guessing it is failing on the main element of the xml message because of some namespace issue. I am generating the XML using xsl transformationin BPEL and sending the XML payload to B2B Service.
Is there a way to know what part of the XML is erroring duing the validation on the server. The error message is not helpful even I turned on Trace 32 level.
Any ideas?
Thank you
Krishna

Order of the validation error for mandatory properties

Hi,
I have created mandatory Properties in KM Configuration.I have configured in such a way that the properties are shown while uploading a file.Now when I upload a file without filling the properties it shows the validation error for the properties but it is not shown in the order of the properties mentioned in the property Groups.
Everytime the error is shown in a random order.
Please advise me whether I am missing something in the configuration.
Thanks in advance
Sowjanya.

Hi,
is it possible, that someone inserted data with a different GC as parameter than your actual group currency is?
otherwise: I had the same problem, but I actually don't know the reason. I changed the validation rule:
before i had: VAL_YTD( write-offs cap. assets BS ) = VAL_YTD( write-offs PL)
now i have: ABS( VAL_YTD( write-offs cap. assets BS ) ) = ABS( VAL_YTD( write-offs PL) )
ABS = absolute value (no sign, only values).
You could also do it like that: ABS( VAL_YTD( write-offs cap. assets BS ) ) - ABS( VAL_YTD( write-offs PL) ) = 0
PS: To have the amount 0 in a validation rule is a restricted perspective. Never forget that!
Not only for the validation - it is always absolutely important to make sure which perspective you have choosen. Check the parameters, check the rules, the selections etc.
BR

Form validation error with mandatory fields and signature field

Hello,
I have seen that many other users are facing this issue, and they partialy do solve it with some workarounds. However, none of them applies to my case.
I have a dynamic form (can be registration form for example) where user fills in bunch of fields. Some of them are mandatory.
When user signs the form, I get our favourite validation error popups that filed this and this did not validate. (I think that the signature is not valid too once I get these errors).
Workaround would be to set all fileds in the form as optional, however, the presign and postsign events work only in A9 and I need the form to be compatible with ver. 8 too.
I also need to make sure, that they are not set to optional, if the signing fails, user clicks on cancel etc...
Any ideas how to acomplish such a scenario?
Thanks
J.

solved by myself.
You have to install and configure the reader rights credentials mentioned in note 736902

XML Payload Validator SAP PI 7.1

Boas
Estou com um problema em um interface, mais propriamente em um campo do mesmo que é um string (50). E este campo esta a ser enviado com 51 caracteres, e mesmo assim o PI aceita sem qualquer tipo de validação anterior, o que vai gerar um dump na maquina destino. Estive a ver e é possível usar um XML Validator, alguém me pode explicar como é que funciona ao certo. Ja estive a ler e sei que e necessário importar o XSD e depois colocar no root do PI, mas mais que isso não sei.
Obrigado
Ruben Catrona

No PI 7.1 existe a funcionalidade sim.
A validacao é baseada na definicao da sua messagem no service interface. No caso, vc tem q definir no Data Type que o tamanho maximo do campo é 50 (ou no XSD a partir do qual a interface foi criada).
Veja o item 3 aqui:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
E esse link:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/0bf1b3ec732d2fe10000000a11466f/frameset.htm
Abs,
Henrique.

Getting Validation Error at B2B Console for 856 Outbound B2B-51507

Hi,
We are getting this error while sending the EDI 856 in an outgoing Process. We are getting the data from Oracle Apps and sending it to B2B via B2b adapter using mediator.
we are using X856 ecx file and X856 xsd.
Can Anyone help in this. If Anyone is having any idea please help us on this.
Do we need to set the Deployment Validation Property to False? If yes then is it in EM we need to Set?
Appreciate quick response.
Below is the error details:
Id 0AF6038D12BE3AE21CF0000011881680
Message Id 0AF6038D12BE3AE1C5E0000011881630
Refer To Message Refer To Message
Sender Type Specialties
Receiver Type Name
Receiver Value XXXX_4010
Sender Sybron Dental Specialties
Receiver :XXXX_4010
Agreement Id:XXXXXXX
Agreement HEN_KRR_AGR
Document Type 856
Document Protocol EDI_X12
Document Version 4010
Message Type REQ
Direction OUTBOUND
State MSG_ERROR
Acknowledgement Mode NONE
Response Mode NONE
Send Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
Receive Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
Document Retry Interval 0
Document Remaining Retry 0
Native Message Size
Translated Message Size 3811
Business Action Name
Business Transaction Name
Xpath Name1 XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2 XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3 XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message Wire Message
Application Message Application Message
Payload Storage Payload Storage
Attachment Attachment
Label soa_b2b_ - Fri Oct 22 04:32:37 PDT 2010
Collaboration Id 0AF6038D12BE3AE205B0000011881670
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name Generic File
Exchange Protocol Version 1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code B2B-51507
Error Description Machine Info: (org-vmsosoa.sds.sybrondental.com) Description: Payload validation error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Error Brief : XEngine error.
This is the Application Message we are getting in Error Details:
Document Type 856
Document Definition 856_DocDefHENK
Document Protocol Name EDI_X12
Document Protocol Version 4010
Refer To Application Message Id Refer To Application Message Id
App Conversation Id
App Message property {tracking.compositeInstanceId=11, b2b.documentProtocolVersion=4010, b2b.toTradingPartnerId=HEN_KRR_4010, tracking.ecid=0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz, b2b.fromTradingPartnerId=Sybron Dental Specialties, tracking.conversationId=BPEL, tracking.compositeInstanceCreatedTime=Mon Oct 25 06:57:39 PDT 2010, tracking.parentComponentInstanceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492, MESH_METRICS=null, b2b.documentTypeName=856, tracking.parentReferenceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492:D4AC5730E03F11DFBFC66D8172AE9492:oneway}
Direction OUTBOUND
State MSG_ERROR
Error Code B2B-51507
Error Text Error Brief : XEngine error.
Error Description Error : Mandatory attribute missing: Standard.
Created Date Monday, October 25, 2010 6:57:40 AM GMT-07:00
Modified Date Monday, October 25, 2010 6:57:41 AM GMT-07:00
Message Size 3811
Payload Payload
Business Message Business Message
Retry Interval 0
Reattempt Count 0
Remaining Retry 0
ECID 0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz
Composite Instance Id 11
Parent Composite Instance Id mediator:D4A7EA60E03F11DFBFC66D8172AE9492
Conversation Id BPEL
Domain Name default
Composite Name Generate856ASNOutbound
Composite Version 2.0
Reference Name B2B_GetData

Hi,
It looks like , Payload is not valid as per the ecs/xsd so B2B is giving Payload validation Error.
If Validation is must then validate the payload against ecs/xsd offline and correct.
or you can turn off validation in Agreement (Validation = false) and redeploy the agreement.
Rgds,
Nitesh Jain

Button condition on page item and Validation error Conflict

Hi,
I have a select list page item and a button on page whose condition is based on the select list page item value(eg, If (:P2_item1='val1'){return true;}) with condition type=PL/SQL function returning boolean. This buttons submits the page.
It' coming fine in normal case. However, if I select some value val2 from the list and then click the button, and if there are any validation errors (like mandatory check or email check fail etc), then the button disappears because it evaluates the button condition based on the changed value(val2), but the page has not yet been submitted because of validation errors.
I think this can be solved if I create the button condition based upon database column value instead of page item as db col value won't change until the page is submitted.
This look like very basic use-case and I would like to know if there is any better solution to this problem.
Note: I am using Apex 4.2.1

I don't want to show/hide the button on the change of the page item lov value, so i am not using Dynamic action.
What i was is to make button visible based on a condition(which is based on page item), for which we have condition attribute of a button available.
This is a very common thing where a user chooses the button condition as Value of item/column in expression 1 is null/expr2. But what if the user changes the page item value but it doesn't get submit due to validation error. In that case, the button condition fails.
So, i guess i have to use column name in expression 1, can u tell how to do that?
Expression 1 = IF (:P2_STATUS='val1') then return true;
How to change the above to use db column 'status' instead? Any direct way(like #Status#) or I have to query db to get it using select.
Any alternative approach?

Is Payload Validation in em mandatory?

Similar Messages

Maybe you are looking for