"No payload set" error in CQ5 workflow
I'm trying to programmatically start a workflow from an OSGi service/servlet. Everything seems to work fine, I checked the WorkflowData and the model to verify they are correct. However, when the startWorkflow method runs, it creates a new instance of the workflow, but doesn't set the payload, and i get this in the error.log file:
com.day.cq.workflow.impl.jcr.WorkflowManager No payload set
com.day.cq.workflow.impl.CQWorkflowSession Workflow instance started with model: /etc/workflow/models/skill-request/jcr:content/model and ID: /etc/workflow/instances/2012-07-17/model_2347856755318064 for payload: skill,Software,barmstrong
As far as I can tell, it has the right data, but refuses to set it to the workflow. Any thoughts or hints would be much appreciated.
My code:
protected void doPost(SlingHttpServletRequest request, SlingHttpServletResponse response) throws IOException
String skillname = request.getParameter("skillname");
String skilltype = request.getParameter("skilltype");
String userid = request.getParameter("userid");
// Getting variables ready for a Workflow
ResourceResolver resourceResolver = null;
Session session = null;
try {
SlingHttpServletRequest slingReq = (SlingHttpServletRequest) request;
session = slingReq.getResourceResolver().adaptTo(Session.class);
WorkflowSession wfSession = _workflowService
.getWorkflowSession(session);
String workflowId = "/etc/workflow/models/skill-request/jcr:content/model";
// Starting a Workflow
WorkflowModel model = wfSession.getModel(workflowId);
WorkflowData wfData = wfSession.newWorkflowData("SKILL_DATA",
skillname + "," + skilltype + "," + userid);
Workflow wf = wfSession.startWorkflow(model, wfData);
} catch (WorkflowException e) {
ps.println(e.getMessage());
e.printStackTrace(ps);
} catch (Throwable e){
ps.println(e.getMessage());
e.printStackTrace(ps);
Thanks for the quick response Scott. I tried setting the Object to the path of a repository node:
WorkflowData wfData = wfSession.newWorkflowData("SKILL_DATA", pagepath);
but it still failed to set as the workflow's payload. I also tried starting the dialog from the Sidekick, which does work.Here are the log messages for the two runs (Sidekick run first, failing run second):
POST /etc/workflow/instances HTTP/1.1] com.day.cq.workflow.impl.CQWorkflowSession Workflow instance started with model: /etc/workflow/models/skill-request/jcr:content/model and ID: /etc/workflow/instances/2012-07-17/model_2352496948786228 for payload: /content/icubed_profile_site/index/resources/barmstrong
POST /apps/icubed/skill_request HTTP/1.1] com.day.cq.workflow.impl.CQWorkflowSession Workflow instance started with model: /etc/workflow/models/skill-request/jcr:content/model and ID: /etc/workflow/instances/2012-07-17/model_2352486082873661 for payload: /content/icubed_profile_site/index/resources/barmstrong
Yet the first run sets the payload just fine, while the second sends back the "No payload set" error.
Brian
Similar Messages
-
Having problems with Bridge shutting down after saving photo in PS Cs5,,,,,,,,, Also when i attempt to update either PS or bridge get an error message in Adobe application manger "Error loading updater workflow"
Sorry for the late reply. My email firewall has become a little over zealous & sent a lot of my emails straight to my junk email folder, so I have only just now discovered your reply in my junk mail folder.
The only "don't open files exceeding xxx megabytes" instruction I can find in my Prefs, is in the Bridge Prefs for Thumbnails, & mine is set at 1000mb. The biggest files I handle are bigger than 200mb so I should be able to open a few, not just one.
However, this doesn't explain why I can open a psd format file of 180mb, close it, but then can't open a RAW format file of only 26mb immediately after.
I can open the RAW file only if I restart my computer - very annoying!
However, thanks for the advice about the video card & memory.
So, I'm still stuck as to what the issue is. -
Getting error while publishing workflow using SP designer for SharePoint 2013
Hi,
I am try to setup Workflow manager for our sharepoint applications.
WF manager set ran without any issue.
I registered the SPWorkflow service which succeeded as well. The Workflow service application shows "Workflow is connected"
I am creating a workflow using sharepoint designer using my credential (not Service account). I am able to save it but while publishing, its prompting with an error.
The error says "Errors were found while compiling the workflow.The workflow files were saved but cannot run." Clicking advanced button show
"Microsoft.SharePoint.SPException: We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
at Microsoft.SharePoint.SPScaleOutDatabaseMap.CreateSqlSession(ISPScaleOutDatabaseMapProvider mapProvider, Byte[] compositeKey, Guid forceRefreshVersion, Guid& version)
at Microsoft.SharePoint.SPScaleOutDatabaseCommandExecutor.Execute(ExecuteDelegate operation, ISPScaleOutDatabaseMapProvider mapProvide"
Any help would be highly appreciated
Thanks,Hi,
According to your post, my understanding is that you got error while publishing workflow using SharePoint designer for SharePoint 2013.
Please check whether the Central Admin > Manage Service Application-> “App Management Service” is started.
Please check whether the “Configure service application associations”, ”App Management Service” is already associated.
Then please check whether the “Manage Services on server” and the “App Management Service” is started.
In addition, please try to re-register Workflow Service.
If the issues still exists, please follow the steps in the
Steps to Verify that Server Is Correctly Set Up. After you verified that the server is correctly set up, follow the steps in the
Steps to Troubleshoot Workflow Management Service and
Troubleshooting the Service Bus for Windows Server then retry your action related to publishing workflows
More information:
http://wp.ahcheng.com/2013/03/23/error-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run/
http://sp2013.pro/2013/04/solution-errors-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run-cannot-set-unknown-member/
Best Regards,
Linda Li
Linda Li
TechNet Community Support -
Error while querying workflow message attributes for task
Can some one please help me with this error?
I get this error when I submit a task in worklist app. I have figure out that it is causing due to one payload in the table in the task. If remove that payload I am able to submit the task.
Error while querying workflow message attributes for task a99d1cf3-5e91-4c4a-8660-aeae91bfbec0 with version 5.
Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
oracle.jbo.JboException: Error while querying workflow message attributes.
Error while querying workflow message attributes for task a99d1cf3-5e91-4c4a-8660-aeae91bfbec0 with version 5.
Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
at oracle.bpel.services.datacontrol.XSDDataControl.invokeOperation(XSDDataControl.java:460)
at oracle.adf.model.bean.DCBeanDataControl.invokeMethod(DCBeanDataControl.java:430)
at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:261)
at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1635)
at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2144)
at oracle.adf.model.bean.DCBeanDataControl.invokeOperation(DCBeanDataControl.java:467)
at oracle.adf.model.adapter.AdapterDCService.invokeOperation(AdapterDCService.java:307)Can anybody help me on this?
I did some google but I get this only which is not much helpful.
http://download.oracle.com/docs/cd/E14571_01/core.1111/e10113/chapter_bpm_messages.htm -
Payload set by API but dataObject remains empty and data does not flow
Hi,
We used ADF to programatically set the payload of a new BPM Instance, using JDev 11.1.1.6 and our BPM is also 11.1.1.6. Followed standard documentation.. and payload gets set, and submitted.
firstTask.setPayloadAsElement(payload);
wfSvcClient_.getTaskService().updateTaskOutcome(ctx, firstTask, Utilities.INIT_TASK_SUBMIT_OUTCOME);
When we check in the BPMN for "exiting the initiator activity", we see payload set BUT dataObject with no elements set (empty):
<auditQueryPayload auditId="505000" ciKey="560017">
<serviceOutput>
<element name="execData" detailId="59246" isBusinessIndicator="false"> <value> <task xmlns="http://xmlns.oracle.com/bpel/workflow/task"> ...
<payload> <PurposeOfFiling xmlns="http://xmlns.oracle.com/OR1/OR1_FORMS_V2/PurposeOfFiling">
*<purOrganizationId>C078</purOrganizationId>*
</PurposeOfFiling> </payload>
..... </serviceOutput>
<dataState> <dataObject name="PurposeOfFiling" isBusinessIndicator="false"> <value>
<PurposeOfFiling xmlns="http://xmlns.oracle.com/bpm/bpmobject/BusinessObjects/PurposeOfFiling">
*<purOrganizationId></purOrganizationId>*
</value></dataObject></dataState>
</auditQueryPayload>
On entering the second activity (there is nothing between the first and second activity, i.e. direct link), the form comes up empty.
It appears that in "firstTask.setPayloadAsElement(payload);" the payload is getting set, but the dataObject is empty, and that the dataObject is what is feeding the second activity, and so that is empty.
Is there a way that we can ensure that the payload "feeds" the dataObject?
Or alternatively, that the payload "feeds" the second activity?
How would it be done? Would really appreciate any assistance.
Thanks!
Ali.Thanks Bill.
It was something that I had in an earlier build (when I was looking into payload updates) and had removed.. but I've gone ahead and put it back.
These are my results:
When the BPM Application Output is wired for dataObject -to- dataObject (which I think is the right way to do), then the dataObject still remains empty.
When the BPM Application Output is wired for UI -to- dataObject, then the Instance gets suspended due to uninitializedVariable.
When the BPM Application Output is not wired at all (and Input was never wired to begin with) then dataObject is missing all together.
One thing I noticed (on just trying the first activity by itself) is that the payload is shown in the UI (i.e. task Payload gets into UI). This was the effect of the "updateTask".
However, in case of programatic SUBMIT, the payload is still not passed to the next activity. This appears to be once again because the dataObject itself is not being set.
Also interestingly I found the below BUG request recently (3/22/2013) registered with Oracle, asking for APIs to be able to get/set the actual dataObject:
BUG 16537745 - ABILITY TO ACCESS PROCESS INSTANCE DATAOBJECT VALUES USING API --> Oracle Business Process Management Suite
- I don't have access to the details of it, but I'm guessing that their dataObject was not being set, and so API Access is requested to set it.
However, if there is an existing solution - whereby the dataObject payload can be set (besides the task Payload), I'd much appreciate.
Thanks! -
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. -
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 -
A very helpful response to an earlier question got me to realize the need to instll the latest raw plugin....6.3....
Now when I go to install I get "error loading updating workflow"
any help on this one???
Thanks
I have CS5 using windows 7 on my dell inspiiron 1545 pc......this was an update t cs5 from previously installed cs4
version"PDA file "and "changed PDA file...."
PDA file
12/21/2010 11:35:13 PDApp - Build Version - 1.0.175.0
12/21/2010 11:35:13 PDApp - Logging Level verbosity Set to 4
12/21/2010 11:35:13 PDApp.CommandLineParser - Parsing the command
line provided. Number of command line arguments is 6
12/21/2010 11:35:13 PDApp - DWA AppletID argument not specified on
command line. Trying to find the existing instance
12/21/2010 11:35:13 PDApp - This is the first instance so creating a
thread for listening to the created pipe
12/21/2010 11:35:13 PipeThread - Pipe thread started
12/21/2010 11:35:13 PDApp - Starting AsyncMessageProcessor
12/21/2010 11:35:13 PDApp.AsyncMsgProcessor - AsyncMsgProcessor
initialized...
12/21/2010 11:35:13 PDApp.AsyncMsgProcessor - AsyncMsgProcessor
started. on thread id = 4960
12/21/2010 11:35:13 PDApp - Detecting Applet Database Library file...
12/21/2010 11:35:13 PDApp - Fetching Applet registeration
information...
12/21/2010 11:35:13 PDApp.AppletManager - AppletManager initialize...
12/21/2010 11:35:13 PIM - Build Version - 1.0.175.0
12/21/2010 11:35:13 PIM - Logging Level verbosity Set to 4
12/21/2010 11:35:13 PIM - CREATE PIM Instance ...
12/21/2010 11:35:13 Utilities - File does not exist
12/21/2010 11:35:13 PIM - trying to createOrUpdatePIMDbSchema.
12/21/2010 11:35:13 PIM - Current db schema version on machine 1.
12/21/2010 11:35:13 PIM - Current db schema version to install 1.
12/21/2010 11:35:13 PIM - PIM DB Schema is up to date. Current schema
version is 1.
12/21/2010 11:35:13 PIM - PIM Database is Up To Date.
12/21/2010 11:35:13 PIM - PIMSqlite closeDB status 0
12/21/2010 11:35:13 PIM - FREE PIM Instance ...
12/21/2010 11:35:13 PDApp.AppletManager - Applet database path -
C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\..
12/21/2010 11:35:13 PDApp.AppletManager - PIM library path -
C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\AdobePIM.dll
12/21/2010 11:35:13 PDApp.AppletManager - Loading PIM library...
12/21/2010 11:35:13 PDApp.AppletManager - Getting applet data from
Applet database
12/21/2010 11:35:13 PDApp.AppletManager - All installed pakages
version string (pim_getCurrentPackagesVersion) is
DWA:1.0.172.0|LWA:1.0.175.0|PDApp:1.0.175.0|UWA:1.0.175.0
12/21/2010 11:35:13 PDApp.AppletManager - Registering Applets...
12/21/2010 11:35:13 PDApp.WindowManager - Initializing native
WindowManager
12/21/2010 11:35:13 PDApp.WindowManager - Creating window instance
12/21/2010 11:35:13 PDApp.WindowManager - Checking for appletID and
appletVersion given in CommandLineOptions
12/21/2010 11:35:13 PDApp.WindowManager - Creating APE stage instance
12/21/2010 11:35:15 PDApp.ExternalGateway - MessageHandler
initialized...
12/21/2010 11:35:15 PDApp.ExternalGateway - ExternalGateway
initialized...
12/21/2010 11:35:15 PDApp.ExternalGateway - NativeCommandHandler
initialized...
12/21/2010 11:35:15.431 PDApp.StartupCommand Logging Level verbosity
Set to INFO
12/21/2010 11:35:15.432 PDApp.StartupCommand Processing the startup
Command
12/21/2010 11:35:15.439 PDAPP.AppletManager Starting Applet
registeration...
12/21/2010 11:35:15.457 PDAPP.MainDisplayMediator Looking up for the
Exact versioned applet for ID :UWA_UI
12/21/2010 11:35:15.479 PDAPP.AppletManager Loading Applet: UWA_UI
Version = 1.0
12/21/2010 11:35:15.514 PDApp.ZStringLoader PDAPP SWF - locale set
to - en_US
12/21/2010 11:35:15.570 PDAPP.AppletManager Loading progress0 out of
521002
12/21/2010 11:35:15.572 PDAPP.AppletManager Loading progress65536 out
of 521002
12/21/2010 11:35:15.574 PDAPP.AppletManager Loading progress131072
out of 521002
12/21/2010 11:35:15.583 PDAPP.AppletManager Loading progress196608
out of 521002
12/21/2010 11:35:15.585 PDAPP.AppletManager Loading progress262144
out of 521002
12/21/2010 11:35:15.588 PDAPP.AppletManager Loading progress327680
out of 521002
12/21/2010 11:35:15.590 PDAPP.AppletManager Loading progress393216
out of 521002
12/21/2010 11:35:15.592 PDAPP.AppletManager Loading progress458752
out of 521002
12/21/2010 11:35:15.594 PDAPP.AppletManager Loading progress521002
out of 521002
12/21/2010 11:35:16.023 PDApp.ExternalGateway Recieved Applet Loading
Completion
12/21/2010 11:35:16.027 UWA.ZStringLoader Trying to load ZString for
preferred locale - en_US
12/21/2010 11:35:16.087 UWA.ZStringLoader Applet locale set to -
en_US
12/21/2010 11:35:16.319 UWAApplet.Startup Processing the startup
command
12/21/2010 11:35:16.324 UWA.LoadWorkflowCommand Processing the
LoadWorkflowCommand
12/21/2010 11:35:16 PDApp.AppletManager - Loading Applet - UWA_Native
for WindowID - 1
12/21/2010 11:35:16 UWANative - Build Version - 1.0.175.0
12/21/2010 11:35:16 UWANative - Logging Level verbosity Set to 4
12/21/2010 11:35:16 UWANative - Updater in patch mode
12/21/2010 11:35:16 UWANative - Error in mdbOpenSessionNoCreate 1
12/21/2010 11:35:16 UWANative - Failed to initialize Updater Core
12/21/2010 11:35:20 Utilities - Directory not present
12/21/2010 11:35:20 UWANative - Could not delete the temp folder "".
12/21/2010 11:35:16.594 UWA.LoadWorkflowCommand The start applet did
not return the result xml. Startapplet returned
12/21/2010 11:35:16.595 UWA.LoadWorkflowCommand Cannot start
UWANative Applet
12/21/2010 11:35:20 PDApp.AppletManager - Un-loading Applet -
UWA_Native for window ID - 1
12/21/2010 11:35:20 PDApp.ExternalGateway - Callng the finalize
function of the applet
12/21/2010 11:35:20 PDApp.ExternalGateway - Unloading applet
12/21/2010 11:35:20.878 PDApp.HostMessageHandler Recieved force
window close message
12/21/2010 11:35:20.878 PDApp.HostMessageHandler Sending message to
native
12/21/2010 11:35:20 PDApp.WindowManager - Window destruction reached
for ID - 1
12/21/2010 11:35:21 PipeThread - Pipe Connected. Waiting for data to
come on pipe
12/21/2010 11:35:21 PipeThread - 2 bytes read on pipe
12/21/2010 11:35:21 PipeThread - Data recieved on pipe. Sending the
data to the main thread to process and show window
12/21/2010 11:35:21 PipeThread - Message Sent to main thread
12/21/2010 11:35:21 PipeThread - Disconnecting pipe
12/21/2010 11:35:21 PipeThread - Pipe Disconnected
12/21/2010 11:35:21 PipeThread - Terminating the pipe thread
12/21/2010 11:35:21 PDApp - Terminating native MessageQueueManager
12/21/2010 11:35:21 PDApp - Terminating native AppletManager
12/21/2010 11:35:21 PDApp.AppletManager - AppletManager destructed
12/21/2010 11:35:21 PDApp - Terminating WindowManager
12/21/2010 11:35:21 PDApp.WindowManager - Destroying PDApp main
window's
12/21/2010 11:35:21 PDApp.WindowManager - Destroying PDApp main
window's sucessfully
12/21/2010 11:35:21 PDApp - Terminating ExternalGateway
12/21/2010 11:35:21 PDApp.ExternalGateway - ExternalGateway
destructed
12/21/2010 11:35:21 PDApp - Terminating MessageHandler
12/21/2010 11:35:21 PDApp.ExternalGateway - MessageHandler
finalize...
12/21/2010 11:35:21 PDApp.ExternalGateway - MessageHandler destructed
12/21/2010 11:35:21 PDApp - Terminating NativeCommandHandler
12/21/2010 11:35:21 PDApp.ExternalGateway - NativeCommandHandler
destructed
12/21/2010 11:35:21 PDApp - Terminating AsyncMessageProcessor
12/21/2010 11:35:21 PDApp.AsyncMsgProcessor - Destroying
AsyncMsgProcessor
12/21/2010 11:35:21 PDApp - Terminating NativePlatformHandler
12/21/2010 11:35:21 PDApp - Terminating logger
PDA changed file
12/21/2010 03:00:24 AAMUpdatesNotifier - Build Version - 1.0.175.0
12/21/2010 03:00:24 AAMUpdatesNotifier - Logging Level verbosity Set
to 4
12/21/2010 03:00:27 Utilities - File does not exist
12/21/2010 03:00:41 AAMUpdatesNotifier - CFU .... StatusCode(41)
ErrorCode(212)
12/21/2010 03:00:41 AAMUpdatesNotifier - inside getUpdates
12/21/2010 03:00:41 AAMUpdatesNotifier - Cannot find any update Node
12/21/2010 03:00:41 AAMUpdatesNotifier - All updates count 0 -
About ale error handling in workflow?
Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phaniHi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1. Create custom BOR object with the events, Start and Stop event
2. Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3. Creation of Function Module and attachment with the Process Code
4. Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani. -
Outbound Idoc error handling through workflow
Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AMHi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow -
OUTBOUND- ERROR HANDLING USING WORKFLOW
Hi Gurus,
Can any one tell me about workflow & how to do error handling using WORKFLOW in OUTBOUND IDOC.Below are the points , Please check it & send me reply.
1.Value not found for Custom IDoc fields.
2. Partner Profile not maintained correctly.
3. Syntax error in IDoc.
4. IDoc ready for dispatch (ALE Service).
Regards,
Chiranjeevi.Hi,
FOr most of your requirements, there is already std. SAP IDOC error Single-step tasks.
Have a look at WE46 transaction.
Also, if you go to SWO1 and search with "IDOC*", you will get all the BO's even.
It's pretty straightfwd. Also, in Partner Profiles, WE20, for each of the IDOC type, there is one "Post.Processing AGent", whom if you set up correctly, will be the person receiving this Errored IDOC mails.
Hope this helps
venu -
Error msg in workflow after patching to 11.1.2.1.600
Hi!
We have recently patched to 11.1.2.1.600 for our Planning solution and we get an error msg in workflow.
If the 'Planning Unit Hierarchy' is setup as 'Free form' we get an error message if the users open 'Manage Approvals', select 'Details' for a Planning Unit and then 'Change status'. The error message is 'There is no valid action that can be performed on the selected Planning Units'. If the 'Planning Unit Hierarchy' is set up as 'Bottom up' it works fine.
Have anyone else experienced this behavior in the 11.1.2.1.600-patch? Is there a workaround?
An SR is also raised towards Oracle, so hopefully we get an answer from them soon.
Grateful for all answers!
BR,
MartinWe're having this issue after installing the 11.1.2.1.600 patch over .102 as well (this didn't come up as known issue), and the workaround of "use Bottom Up" doesn't work for us, because we want multiple planners in an organizational division to be able to write to the same PU at the same time. You can't do that with Bottom Up, because only one person can have control at a time.
So... the .601 patch still doesn't exist, and uninstalling the .600 patch didn't fix the issue. Support basically says, "it's a bug, use the workaround".
So frustrating! -
Error in starting workflow queue listener
I have registered jobs with OEM using Warehouse builder workflow deployment
wizard. Following jobs has been registerd with OEM :
1) ACRM_IWF_ACRM_PWF
2)ACRM_IWF_OWB_STD_BEGIN
3) ACRM_IWF_OWB_STD_END
4) ACRM_IWF_OWB_STD_ERROR
Now i submit "ACRM_IWF_ACRM_PWF" from the OEM . I shows me status of the JOB as
"Failed" and gives the following error message:
Error in starting workflow listener: ** Initializing queue listener
** Initialized queue listener
** Recovering item type ACRM_IWF
** In recovery mode
** Recovery complete
** Processing all item types
** Waiting to dequeue message in listener
** Processing job 0x4143524D5F4957465F4F57425F5354445F424547494E
Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
at java.lang.String.substring(String.java:1085)
at
oracle.wh.runtime.workflowrt.QueueListener.parseParameters(QueueListener.java:10
03)
at oracle.wh.runtime.workflowrt.QueueListener.startJob(QueueListener.java:798)
at
oracle.wh.runtime.workflowrt.QueueListener.processJobs(QueueListener.java:746)
at
oracle.wh.runtime.workflowrt.QueueListener.initAndRun(QueueListener.java:299)
at oracle.wh.runtime.workflowrt.QueueListener.main(QueueListener.java:197)
1This is not actually a Workflow component, this is part of the Oracle Warehouse Builder product, although the name is similar to the Workflow Agent Listener in v2.6.
I have registered jobs with OEM using Warehouse builder workflow deployment
wizard. Following jobs has been registerd with OEM :
1) ACRM_IWF_ACRM_PWF
2)ACRM_IWF_OWB_STD_BEGIN
3) ACRM_IWF_OWB_STD_END
4) ACRM_IWF_OWB_STD_ERROR
Now i submit "ACRM_IWF_ACRM_PWF" from the OEM . I shows me status of the JOB as
"Failed" and gives the following error message:
Error in starting workflow listener: ** Initializing queue listener
** Initialized queue listener
** Recovering item type ACRM_IWF
** In recovery mode
** Recovery complete
** Processing all item types
** Waiting to dequeue message in listener
** Processing job 0x4143524D5F4957465F4F57425F5354445F424547494E
Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
at java.lang.String.substring(String.java:1085)
at
oracle.wh.runtime.workflowrt.QueueListener.parseParameters(QueueListener.java:10
03)
at oracle.wh.runtime.workflowrt.QueueListener.startJob(QueueListener.java:798)
at
oracle.wh.runtime.workflowrt.QueueListener.processJobs(QueueListener.java:746)
at
oracle.wh.runtime.workflowrt.QueueListener.initAndRun(QueueListener.java:299)
at oracle.wh.runtime.workflowrt.QueueListener.main(QueueListener.java:197)
1 -
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 -
Object variable not set (Error 91) in Input Enabled query
Hello,
I'm having the following issue. I have created an input enabled query and included it in a planning workbook. Every time I open the workbook or query, and I got to an input enabled cell, I get the error below:
Object variable not set (Error 91)
This client has not used planning workbooks before. The system is on 7.10 SP10 for Bex Analyzer and SAP Gui 7.10 Patch Level 13.
I'm not finding any relevant so far in SDN. Any help anyone can provide is greatly appreciated.
Thanks,
SenthilHello,
Just wanted to let you all know that this issue has been resolved after updating my SAP Gui to 7.2 Patch Level 4 (Patch Level 5 was causing some other issues so I decided to stay at Level 4).
Thanks,
Senthil
Maybe you are looking for
-
Functunality of save view in BW report iview
Dear all, When SAP BW Query report iview is called in portal, u will get Save view, Bookmark, variableSreen...etc buttons.. When u click on saveview button...it will ask u to save as a view of that report with specific name. My question is, where it
-
Apple Remote Desktop and Itunes
I am using Apple remote desktop to connect to several servers with several users on each server. When Itunes is playing and I try to fast user switch, it will stop playing itunes on the user I am switching from. Is anyone familiar with any problems l
-
Photo editing and occasional video stuff - which Macbook Pro for me?
Hi guys! I'm seriously considering buying a Macbook Pro to replace my current desktop PC. My intuition is telling me to get 16GB of RAM and to not settle for a two core processor. This, however, isn't too easy on the wallet. I do photo editing quite
-
Redolog01,02,03 size
Dear Team , My redolog01,redolog02,redolog03 size is 50mb . Can I resize to 250 or 500 mb and its not affact anything on my database .. and restart databse required or not . Thanks Abu shahd
-
Any software/program that can read audit log files
Hi, Currently i am searching for a program/tools that can read audit log files and format it into a readable format. Anyone know is there any in the market or any open source program? Thank You.