OWB Workflow Error

Hi,
I have some workflows designed using OWB. We have automated them using Cron. The jobs run fine everyday, provided the client is connected to the OWB design center and the listener. If for some reason the client is not logged into design centre, the entire job just hangs. When the client connects back to the design centre, the job terminates with the following error:
Error
RPE-01003: An infrastructure condition prevented the request from completing.
Error
ORA-20003: The object is not in a valid state for the requested operation
ORA-06512: at "PRD_OWB.WB_RTI_EXCEPTIONS", line 119
ORA-06512: at "PRD_OWB.WB_RTI_SERVICE_EXECUTION", line 834
ORA-06512: at "PRD_OWB.WB_RT_SERVICE_CONTROL", line 188
ORA-06512: at line 1
RECOVERY
RPE-01008: Recovery of this request is in progress.
Error
ORA-20002: 3122: Duplicate item 'PO_MOD/WB_IK_20060811_073457_24714' could not be created.
ORA-06512: at "OWF_MGR.WF_ENGINE", line 3920
ORA-06512: at line 1
Can anyone explain what this means ?
How do you make the running of the jobs independent of whether the client is connected to the design center and listener. This is urgent -- pls help !
Thanks
Rita

It looks like you are launching the workflow with an item key that you already used earlyier.
The item key must be unique!
ORA-20002: 3122: Duplicate item 'PO_MOD/WB_IK_20060811_073457_24714' could not be created.

Similar Messages

  • OWB workflow question

    I'm an OWB-newbie (using PARIS) and have a question about OWB workflows.
    I want to create several mapping workflows.
    All the mapping workflows should send a mail with the outcome of the workflows (success, error, warning) to an administrator.
    I don't want to always code the same mail activity with the same parameter values.
    So my idea is to write one subprocess which handles the mail-routine with some input parameters (calling workflow-name, process state (success, warning, error)).
    In the subprocess I want to test the input parameter "process-state". If the value is 0 (success) then a mail with the workflow name as subject should be generated incuding an static text e.g. "mapping successful". If the value is 1 then "mapping warning" and so on.
    What OWB activity has to be choosen for testing the input parameter "process-state" like an if-then-else construct or a case-construct?
    How can the value of the input parameter "workflow-name" be included in the mail-body?
    Regards
    Martin

    To my experience, using the OWF for these things is not very practical. I would suggest that you would make your own PL/SQL procedude that does this, and then call that procedure from within the actual mapping (post-mapping), using the values you have there.
    This might not be what you want, however. I simply find the email capabilities of OWF too limited for actual work.

  • Start OWB workflow from APEX

    Hi together,
    My challenge is to start an OWB workflow from an apex procedure.
    Procedure:
    declare
    numb number;
    audit_id number;
    begin
    numb := rtruser_blueprint.exec_api.execute('LOC_A014_OWF_MGR', 'PROCESS', 'LOAD_CALM_DELIVERY', ',', 'DELIVERY_ID_IN=6', audit_id);
    end;
    My problem is the following error:
    ORA-06565: cannot execute SET ROLE from within stored procedure
    This error occures at the following row in the execute-Procedure in the package exec_api (standard owb execution package):
    dbms_session.SET_ROLE('OWB_D_rtr10201_blueprint');
    dbms_session.SET_ROLE('OWB_O_rtr10201_blueprint');
    If I run this script directly with sqlplus, the procedure works fine. As a result of this, I assume, the problem has to do with the grants which the apex execution user (APEX_PUBLIC_USER) doesn't have in contrast to the blueprint user (which is schema owner)
    More informations about the environment setup:
    The apex workspace is bound to the database - user: BLUEPRINT.
    BLUEPRINT has the grant to execute the procedure 'EXECUTE' in the package 'EXEC_API'. The 'EXEC_API' package belongs to the user 'RTRUSER_BLUEPRINT'.
    My concrete question is: Which rights / grants does which user need to execute the procedure directly from APEX?
    Thanks for your help!
    Mirco

    What account were you using when you ran the 'execute_api' procedure from SqlPlus ? Also, all SQL and PL/SQL from APEX is executed as the application's parsing schema id and not the schema used by APEX to connect to the database.

  • Configure the Database for FTP in an OWB workflow

    I want to use the ftp-operator in an OWB-Workflow. I want to use a script, that is managed in the owb itself.
    I configure the ftp operator in this way:
    COMMAND: /usr/bin/ftp (i can start the command at the command line)
    PARAMETER_LIST: ?"${Task.Input}"?
    SUCCESS_THRESHOLD: 0
    SCRIPT: [my with the ftp Commands]
    After the execution of the workflow i get the error message: "/usr/bin/ftp -n: not found"
    in Runtime Audit Browser
    Does anybody know what i have to do to get the ftp operator running?
    The operating system of the database server is HP UX.
    Thanks in advance
    Alexander

    Hi,
    why do you want to use ftp? As against going directly to the source database? (So much faster and easier). I haven't used ftp since the last century.
    Regards,
    Donna

  • Workflow Error Message: System Account - The Workflow could not set Content Approval Status

    This is the first time I try an approval workflow. I am using a template in MS Word and assigned an approval workflow to it. The approval workflow is only going to one person in this case.
    When I start the work flow the following 3 error messages show up:
    Workflow Error Message: System Account - The Workflow could not set Content Approval Status. Enable content moderation for this list and run the workflow again.
    Workflow Error Message: System Account - The e-mail message cannot be sent. Make sure the e-mail has a valid recipient.
    Workflow Error Message: System Account - The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly.
    Thank you for your kind guidance.

    Hi,
    For the first error: Did you set Content Approval in the workflow?  If so, see if you have it in the versioning settings of the list settings.
    For the second error: double check your recipient is set up as being valid.  Did you type in the email address or is it referring to a people picker field?  also, make sure that in the workflow for the email that you actually populated it in the
    To: field.
    for the third error: I suspect that either your farm is not configured for email.  Or, this error is a knock on from the second error.  If you get the second error rectified it may clear this error.  If not then double check the email settings
    for your farm.
    Johnathan Lightfoot

  • Workflow error when submitting Employment Verification Letter in ESS Portal

    in ESS Portal, when trying to send the employment verification letter by mail I get a workflow error in ECC. Error occurs in workflow template WS01000045 (Employment and Salary Verification) task TS00408262 (PF: Find basic pay). The employee submitting the verification letter request is an active employee, has infotype 105 data in the system, and has basic pay data in the system.
    workflow log (SWI1) shows the "Basic Pay" object available and when double clicking on the object, it brings me to PA20 where I can see the Basic Pay infotype with correct data.
    Can someone help?
    note: the employee is Canadian, in case this matters.
    Tiberiu

    Have you created the resposibilities for the rule 60100010 becuase if you observe the rule it will determine the agents by using the category Agent Determination: Reponsibilities so i think you missed to create responsibilities
    for creating responsibilities [check|http://help.sap.com/saphelp_nw70/helpdata/EN/ef/3dc9469bbe11d189470000e8216659/content.htm]
    Also check that if Rule fails to determine the agents correctly then how can you [handle|http://help.sap.com/saphelp_nw70/helpdata/EN/7f/aed54c9c8d11d1894c0000e8216659/content.htm]

  • OWB Workflow Help

    Im conducting a proof of concept using OWB Workflow version 2.4. To give some background, the objective is to run numerous dependant SQL scripts that in effect hand craft the ETL process, at a pre-scheduled time, that provide logging and re-starting functionality.
    With the distinct lack of publications and documentations Id appreciate any feedback anyone may have on the following:
    1) Is it possible to restart a process at a step midway through the flow. For example the 3rd SQL Activity step out of 10 may have failed and instead of starting over, its a requirement to re-start the step that failed.
    2) I've read that Oracle are rumoured to be de-supporting the workflow functionality, if so then what is their proposed method of scheduling and controlling ETL jobs.
    3) Can a log file generated by the SQL Plus activity be attached to the failure or success email activity?
    Any input would be appreciated, also any pointers to OWB publications or documentation, other than the Oracle manuals of course.
    Thanks in advance
    James

    We have been working towards something similar, and the approach we have settled on is as follows:
    1) We have added our own runtime-audit tables which track the most recent process flow run date, final status, and the completion status of each mapping. So, a new run can see if a) this run is a restart, in which case we set our max date for drawing data over to be the run date of the last run, and b) what mappings ran succesfully. This way, a function called needs_to_run(mapping_name varchar2) returns a true/false answer to see if a given mapping needs to be executed on this run. The logic is pretty simple
    if run_type is full_run or (run_type is restart and nvl(last_run_status,'FAILURE') of this mapping is 'FAILURE')
    then
    return true;
    else
    return false;
    2) We do not use mapping objects in the process flows. We will only use SQL*Plus objects that do something like this:
    variable exec_return_code;
    declare
    retVal varchar2(30) := 'OK';
    begin
    if needs_to_run('ThisMapping') then
    ThisMapping.main(retVal);
    end if;
    :exec_return_code := retVal;
    exception
    when others then
    :exec_return_code := 'FAILURE';
    end;
    exit :exec_return_code
    So that each mapping will check first to see if it needs to execute before running thus skipping over fully completed mappings in the case of a restart. As to emailing log information, we currently do that in our post-mapping procedures in the event of a failure rather than logging to file and then attaching to email. We also have a last step that emails a summary of our audit info for each mapping run - but again this is all done inside pl/sql rather than spooling to file.
    Anyway, just some ideas to toss your way. And no, we haven't yet got it all completed and working yet, but it is coming along nicely and none of our individual proof-of-concept tests have provided us with any show-stoppers thus far.
    Cheers,
    Mike

  • Service Manager 2012 R2 - Workflow Error - Event ID 4513

    Hi,
    We started to suffer a Workflow error in Service Manager 2012 R2 2 weeks ago. We noticed through the failure of some SLOs not being applied on Work Items. The error is the follow:
    Log Name:      Operations Manager
    Source:        HealthService
    Date:          13/03/2014 12:10:00
    Event ID:      4513
    Task Category: Health Service
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XXX-XXX-XXX
    Description:
    The callback method DeliverDataToModule failed with exception "'­', hexadecimal value 0x1F, is an invalid character." in the module Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.
    Workflow: WorkItem_SetFirstAssingedTo_RelationhsipAdd_Rule
    Instance: Destino do Fluxo de Trabalho (interno)
    Instance ID: {383E578B-E1C9-2802-0047-815853405778}
    Management Group: CTRPROD
    Full Exception Text:
     System.ArgumentException: '­', hexadecimal value 0x1F, is an invalid character.
       at System.Xml.XmlEncodedRawTextWriter.InvalidXmlChar(Int32 ch, Char* pDst, Boolean entitize)
       at System.Xml.XmlEncodedRawTextWriter.WriteElementTextBlock(Char* pSrc, Char* pSrcEnd)
       at System.Xml.XmlEncodedRawTextWriter.WriteString(String text)
       at System.Xml.XmlWellFormedWriter.WriteValue(String value)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiType(XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle objectTypeHandle, Type objectType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, Type
    declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteArrayOfanyTypeToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
       at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteResultToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
       at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.WriteObject(XmlWriter writer, Object graph)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.DataItemSubscription.GenerateItemXml(XmlWriter writer)
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GenerateItemXmlInternal()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GetItemXml()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.QueryItem(XPathExpression xpathQuery)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.TokenResolver(String tokenValue)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.RegexMatchEvaluator(Match m)
       at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat)
       at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.Resolve(String str)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.GenerateWindowsWorkflowTaskParameterValue(String elementTemplate)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskParameterValue.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskArrayParameter.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTask.Resolve(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.ProcessDataItems(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.OnNewDataItems(DataItemBase[] dataItems, Boolean isLogicalSet, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback
    completionCallback, Object completionState)
       at Microsoft.EnterpriseManagement.HealthService.Internal.InputPortCallbacks.InputStreamBatchedAcknowledgedCallbackHandler`1.InputPortCallbackImplementation(DataItemBase[] dataItems, Boolean isBatchLogicalSet, DataItemAcknowledgementCallback
    acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ModuleContainer`1.Microsoft.EnterpriseManagement.HealthService.Internal.IModuleContainer.DeliverDataToModule(UInt32 inputPortNumber, DataItemBase[] dataItems, Boolean isBatchLogicalSet,
    DataItemAcknowledgementCallback acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.Microsoft.EnterpriseManagement.HealthService.Internal.IManagedHostHelper.DeliverBatchedDataToModule(UInt32 inputPortNumber, Object moduleInputReference, DataItemBase[]
    dataItems, UInt32 dataItemCount, Boolean isBatchLogicalSet, Object completionReference)
    Event Xml:
    <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='HealthService'/><EventID Qualifiers='49152'>4513</EventID><Level>2</Level><Task>1</Task><Keywords>0x80000000000000</Keywords><TimeCreated
    SystemTime='2014-03-13T15:10:00.000000000Z'/><EventRecordID>4953905</EventRecordID><Channel>Operations Manager</Channel><Computer>CTR-SCSM-MS01.sp.local</Computer><Security/></System><EventData><Data>CTRPROD</Data><Data>WorkItem_SetFirstAssingedTo_RelationhsipAdd_Rule</Data><Data>Destino
    do Fluxo de Trabalho (interno)</Data><Data>{383E578B-E1C9-2802-0047-815853405778}</Data><Data>DeliverDataToModule</Data><Data>'­', hexadecimal value 0x1F, is an invalid character.</Data><Data>Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction</Data><Data>System.ArgumentException:
    '­', hexadecimal value 0x1F, is an invalid character.
       at System.Xml.XmlEncodedRawTextWriter.InvalidXmlChar(Int32 ch, Char* pDst, Boolean entitize)
       at System.Xml.XmlEncodedRawTextWriter.WriteElementTextBlock(Char* pSrc, Char* pSrcEnd)
       at System.Xml.XmlEncodedRawTextWriter.WriteString(String text)
       at System.Xml.XmlWellFormedWriter.WriteValue(String value)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiType(XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle objectTypeHandle, Type objectType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, Type
    declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteArrayOfanyTypeToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
       at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteResultToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
       at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.WriteObject(XmlWriter writer, Object graph)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.DataItemSubscription.GenerateItemXml(XmlWriter writer)
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GenerateItemXmlInternal()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GetItemXml()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.QueryItem(XPathExpression xpathQuery)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.TokenResolver(String tokenValue)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.RegexMatchEvaluator(Match m)
       at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat)
       at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.Resolve(String str)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.GenerateWindowsWorkflowTaskParameterValue(String elementTemplate)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskParameterValue.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskArrayParameter.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTask.Resolve(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.ProcessDataItems(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.OnNewDataItems(DataItemBase[] dataItems, Boolean isLogicalSet, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback
    completionCallback, Object completionState)
       at Microsoft.EnterpriseManagement.HealthService.Internal.InputPortCallbacks.InputStreamBatchedAcknowledgedCallbackHandler`1.InputPortCallbackImplementation(DataItemBase[] dataItems, Boolean isBatchLogicalSet, DataItemAcknowledgementCallback
    acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ModuleContainer`1.Microsoft.EnterpriseManagement.HealthService.Internal.IModuleContainer.DeliverDataToModule(UInt32 inputPortNumber, DataItemBase[] dataItems, Boolean isBatchLogicalSet,
    DataItemAcknowledgementCallback acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.Microsoft.EnterpriseManagement.HealthService.Internal.IManagedHostHelper.DeliverBatchedDataToModule(UInt32 inputPortNumber, Object moduleInputReference, DataItemBase[]
    dataItems, UInt32 dataItemCount, Boolean isBatchLogicalSet, Object completionReference)</Data></EventData></Event>
    Has anybody faced the same problem?
    Thanks
    Thiago

    Hi Thomas,
    Thanks for your response. I understood your comments but, the system was running fine for about 3 months. No changes have been applied during this time and suddenly this error pops out.
    I opened a case with MS Support, but they applied a WA which does not resolve our problem, because the error appears after a few days later after the WA procedure.
    The WA is just a watermark reset using this SQL query:
    DECLARE @MaxTransactionId Int, @RuleID uniqueidentifier
    SET @RuleID = '' -- <-- SET THIS TO YOUR RULE ID!!!
    SET @MaxTransactionId = (SELECT MAX(EntityTransactionLogId) FROM EntityTransactionLog) 
    UPDATE CmdbInstanceSubscriptionState
    SET State = @MaxTransactionId
    WHERE RuleId = @RuleID
    The problem with this WA is that all Work Items affected by the problem - workflows not being applied - do not get the information we need to identify all the SLA's. The system just "forget" them and moves on.
    Cheers,
    Thiago

  • Sales Agreement workflow errored on 3205: is not a valid role or user name.

    Hi experts,
    We're currently on EBS R12.1.2 We're running into an issue that seems like a very general issue that other businesses would have encountered before. We have a business user who creates most of sales agreements. When this business user left the company, we set active end date on the particular userid. Now, when we go into these sales agreements originally created by this particular userid, and put in the expiration date to expire these sales agreement. We're seeing the sales agreement workflow erroring out in the pre-notification workflow email with error 3205: is not a valid role or user name.
    It seems to be this is a very typical business scenario. If you have encountered this problem, please share how you resolved this issue within your oracle apps environment.
    Thank you in advance for your help,
    Jennifer

    Hello,
    We have the same problem in 11.5.10.2. If we want use this blanket sales agreement I have to skipped this notification by sysadmin and after this I can extend end date and another user can use this BSA.
    Look at Extend The Expiration Date For Closed Non-Active Expired BSA Blanket Sales Agreement [ID 1394888.1]     
    Regards,
    Luko

  • Modifying workflow error message

    Dear all,
    i have a requirement where i need to modify the workflow error and i need to enter additional information like customer number and customer purchase order number in workflow error message and error description during inbound Idoc processing.
    can anybody explain me how it can be achieved?
    thanking you in anticipation
    Ashvin Patel
    Edited by: Ashvin Patel on Dec 25, 2008 8:09 AM

    Dear Krupa,
    Thnx for the reply, but can you pls elaborate it. as i need to write a FS for this but i don't know how to put this in technical terms.
    Regards
    Ashvin Patel

  • Workflow error in ChaRM using Group Approval

    Hi,
    I am using the Group Approval in ChaRM's requests for change transactions, as explained in detail in Michael Vollmer's blogpostNew ChaRM Feature with SP 10: Enhanced Approval Procedure Functions
    I am also using the workflow crm_rfc_aprv (WS17100016), which sends out workflow tasks during the approval procedure.
    Since I have assigned organizational units to my approval procedure, I always receive an e-mail from the Workflow User with title "Workflow 12345 set to status ERROR" for every ticket.
    This is because somewhere in the code behind the workflow, a user is searched based on the business partner in the approval step. But an Organizational Unit is never linked to a user, you cannot assign the BP Role "employee" to an organizational unit.
    It would be nice if the workflow could send workflow tasks to all the users assigned in the organizational model to the organizational unit. But currently, I am most concerned with getting rid of the workflow error e-mails. I really don't want to get an e-mail for each and every ticket.
    Does anyone know if there is a way to solve this? Maybe some way to link an organizational unit to a (dummy) user anyway?

    Hi Karthik,
    Yes, my organizational model is maintained.
    There are three BP's + Users assigned to the organizational unit.
    The SP10 Enhanced Approval Procedure completely works, those three users are able to set the approval for the "Center of Competence" organizational unit to "approved" in the RfC ticket.
    However, the workflow behind it never goes looking in the organizational model. It just sees "business partner 632", and checks only the data of BP 632, and doesn't find a user on it. So the workflow goes into error, and sends a mail about it to me...
    For approval step 1 everything goes as normal, there is a specific person assigned to the step, the workflow finds a user on the person's business partner, and sends a workflow task / mail to that user.
    Below are screenshots of tx PPOMA_CRM, the approval block in the RfC ticket, and the correct and error mail as seen in the tx SOST list.
    Kind regards,
    Joyca

  • Calling owb workflow job created in oem using pl/sql

    is it possible using pl/sql to call owb workflow job which is created thru oem
    can you pl be kind enough to share a sample.
    thanks

    Hi,
    The same question was just answered by another member a couple a days ago want to run owb mappings thru job schedule :
    sqlplus_exec_template runtime_owner location_name PROCESS process_name "," ","
    sqlplus_exec_template is in "D:\oracle\oraWB\owb\rtp\sql"
    Nikolai Rochnik

  • Workflow error when sending Verification Letter request by mail

    in ESS Portal, when trying to send the employment verification letter by mail I get a workflow error in ECC. Error occurs in workflow template WS01000045 (Employment and Salary Verification) task TS00408262 (PF: Find basic pay). The employee submitting the verification letter request is an active employee, has infotype 105 data in the system, and has basic pay data in the system.
    workflow log (SWI1) shows the "Basic Pay" object available and when double clicking on the object, it brings me to PA20 where I can see the Basic Pay infotype with correct data.
    Can someone help?
    note: the employee is Canadian, in case this matters.
    Tiberiu

    Once you are satisfied that the origin is satisfactory it is best to select the option worded something like - always accept from this site.
    In my experience it is always more reliable to use the SMTP server which matches your From name. The one exception is running your own SMTP server on a fixed IP.
    Check that your Mail SMTP settings have the correct, name, password, security and port.

  • Workflow error from purchase requisition screen

    How can I check workflow error / status / information from purchase requisition screen. Is there any other transaction ?

    Goto SWI6 or SWI14 and enter the object type (standard is BUS2105 for PR) but in your organization if custom Object type used then enter that and execute you will see the list here
    enter the selection period

  • SRM Workflow error-  Error' 9' when calling service ' SO_OBJECT_SEND'

    Hi Team,
    We are facing problem with SAP SRM Workflow error-  Error' 9' when calling service ' SO_OBJECT_SEND' .
    Due to this WI is not going to Approver/Requester INBOX and unable to process that WI.
    Please advice .
    Greatly Appreciated for Help.
    Regards
    CK

    Hi,
    Not sure what '9' is, the exceptions called by the SO_OBJECT_SEND function are as follows:
    EXCEPTIONS
                   ACTIVE_USER_NOT_EXIST      = 35
                   COMMUNICATION_FAILURE      = 71
                   COMPONENT_NOT_AVAILABLE    = 01
                   FOLDER_NOT_EXIST           = 06
                   FOLDER_NO_AUTHORIZATION    = 05
                   FORWARDER_NOT_EXIST        = 08
                   NOTE_NOT_EXIST             = 45
                   OBJECT_NOT_EXIST           = 13
                   OBJECT_NOT_SENT            = 15
                   OBJECT_NO_AUTHORIZATION    = 13
                   OBJECT_TYPE_NOT_EXIST      = 17
                   OPERATION_NO_AUTHORIZATION = 21
                   OWNER_NOT_EXIST            = 22
                   PARAMETER_ERROR            = 23
                   SUBSTITUTE_NOT_ACTIVE      = 31
                   SUBSTITUTE_NOT_DEFINED     = 32
                   SYSTEM_FAILURE             = 72
                   TOO_MUCH_RECEIVERS         = 73
                   USER_NOT_EXIST             = 46
                   OTHERS                     = 1000.
    Regards,
    Jason

Maybe you are looking for