Order blocked by user / Workflow error handling

Hi Folks,
I am getting this requirement quite often. Time to address it in a more efficient way than that I know.
The following is the requirement:
Workitem goes to approver. If the approver approves/rejects the workitem, there is a subsequent change in the sales order which is handled by BAPI in the next step. If the sales order is locked by some user, BAPI does not make change and throws an error.
Solution that I can think of:
The way it is handled right now is - if there is an error message from BAPI - the workflow is routed to a power user or an email message is sent to admin asking him to inform the right user.
This approach of mine does not sound correct. Can we actually throw error at the time when the approver tries to open the workitem itself (i.e. see if the transaction is being locked and if it is locked - throw an error and do not allow the approver to take action ).
Thanks,
aby.
Hi Aby,
If I understand this correctly, the sales order can be blocked by some other application during the approver's task?
Is the approval task a decision task, or a custom task? If custom, perhaps you could include some locking/unlocking code?
I suppose you could implement a before-method to check for a lock - but you aren't able to pass data back to the approval task from a before method. You could check for a lock in a separate task prior to the approval task, but there is no guarantee that the user would complete the task before someone else locks the object up again.
Another approach might be to check the results of the BAPI, and if it's throwing an 'Object locked' type of error, call it again. Of course, you would need to put some wait time in the BAPI, and also, you would need to ensure it does not go on waiting and trying forever. But nobody likes to admit they put wait steps into anything.
Just a few ideas to consider. I wonder if this problem is that persistent?
Sue

Similar Messages

User friendly error handling in a trigger

Hello,
How can I have user freindly error handling when am using a trigger??
In the trigger I through an exception such I use if statment in the tigger
If ( condition) then
RAISE_APPLICATION_ERROR(-20001, ' Error message');
end if;How can I display this message in uer friendly way??

See Patrick's posts here:
http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/
http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-2/

User defined error handling in PLSQL procedure of portal form

I need some help of building a user defined exception handling in PLSQL.
I build a portal form based on a PLSQL procedure.
In this procedure there are several SQL statements with exception handling.
In case of exception I want to display my on error message and than raise the procedure, so that the user can read the message and than go back to form.
I try this by calling a raise statement generating some HTML output over htp.p() but than the output look's like
SQL:
begin
"ACHEMA2003"."P_LOGIN" ( P_STAMM_SEQ => 33491, P_ADRESSNR => 2009721, P_PASSWORD => '3333', P_PROJEKT_ID => 'ACHEMA2003', P_MESSENR => '00023', P_SPKZ => 'D');
end;
ORA-20000:
Login ACHEMA 2003
Ung|ltiges Passwort !!!
Back to form
I want to supress the standard Oracle messages.
Now I read about the packages wwerr_api_error and wwerr_api_error_ui to make this, but it seems to be a little difficult.
Is there anybody who have a solution for this problem, perhaps some example PLSQL code for this.
Thanks Erwin.

Jacob,
Try following:
declare
v_sender VARCHAR2(1000);
v_sender_id NUMBER;
begin
v_sender := p_session.get_value_as_VARCHAR2(
p_block_name => 'DEFAULT',
p_attribute_name => 'A_SENDER');
v_sender_id := p_session.get_value_as_NUMBER(
p_block_name => 'DEFAULT',
p_attribute_name => 'A_SENDER_ID');
insert into hd (number, text) values (hd_seq.nextval,
'step 3 v_sender = ' || v_sender ||
' v_sender_id = ' || v_sender_id);
if v_sender_id >= 100 then
p_session.set_value(
p_block_name => "_block",
p_attribute_name => '_STATUS',
p_value => 'Sender ID must be less than 100!');
-- return to your form with status message set
-- and all fields filled with recent values
return;
end if;
end;
-- This point is reached only if validation is OK
doInsert;
Regards,
Henn

Collect data from User workflow error updating list item

Hi, can someone please help me with WSS 3 workflows?!
I'll keep it simple - I have a workflow step "Collect data from user" that will fail with Unknown Error when attempting to update list item (this is after the user has clicked Complete Task). The workflow does not continue past this step and I have
to terminate the workflow.
What is odd, is that if I do another Collect data from User in the same step but following the 1st collect, both will work!! How can this be?? This proves the 1st collect is OK so why won't it run without another Collect data after it?! Doesn't make sense to
me.
I was just trying the second Collect to troubleshoot the issue. I've tried other actions there but having another Collect does seem to be the action that kicks things into life. Is there a clue here?
Any clues would be much appreciated as I'm not able to turn much up when I Google.
Thanks

Well, surprise, surprise, this has come back (thought it might!). The trace logs show it's a task locked error but I can't see how. Can anyone please provide me with some clues??
03/14/2014 12:30:25.11    w3wp.exe (0x7698)                          0x5EA4   Windows SharePoint
Services     Web Controls                     88wy   Medium     SPDataSourceView.ExecuteSelect()
- selectArguments: IsEmpty=True, MaximumRows=0, RetrieveTotalRowCount=False, SortExpression=, StartRowIndex=0, TotalRowCount=-1
03/14/2014 12:30:28.39    w3wp.exe (0x7698)                          0x6C4C   Windows SharePoint Services
    Web Controls                     88wy   Medium     SPDataSourceView.ExecuteSelect() - selectArguments:
IsEmpty=True, MaximumRows=0, RetrieveTotalRowCount=False, SortExpression=, StartRowIndex=0, TotalRowCount=-1
03/14/2014 12:30:28.47    w3wp.exe (0x7698)                          0x6C4C   Windows SharePoint Services
    Web Controls                     88wy   Medium     SPDataSourceView.ExecuteSelect() - selectArguments:
IsEmpty=True, MaximumRows=0, RetrieveTotalRowCount=False, SortExpression=, StartRowIndex=0, TotalRowCount=-1
03/14/2014 12:30:29.86    w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          72er   Medium     Microsoft.SharePoint.SPException: This task is currently locked by a running workflow and cannot
be edited.     at Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, SPWeb web, Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object& objAttachmentNames, Object& objAttachmentContents, Int32&
parentFolderId)     at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean
suppressAfterEvents)     at Microsoft.SharePoint.SPListItem.Update()     at Microsoft.SharePoint.Workflow.SPWinOEWSSService.CommitUpdateListItem(Transaction txn, Object[] transData)
03/14/2014 12:30:29.86    w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          72fe   High       Error in commiting pending workflow batch items: Microsoft.SharePoint.SPException: This
task is currently locked by a running workflow and cannot be edited.     at Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, SPWeb web, Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object& objAttachmentNames,
Object& objAttachmentContents, Int32& parentFolderId)     at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion,
Boolean bCheckOut, Boolean bCheckin, Boolean suppressAfterEvents)     at Microsoft.SharePoint.SPListItem.Update()     at Microsoft.SharePoint.Workflow.SPWinOEWSSService.CommitUpdateListItem(Transaction txn, Object[]
transData)     at Micro...
03/14/2014 12:30:29.86*   w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          72fe   High       ...soft.SharePoint.Workflow.SPPendingWork.PerformWorkNow(Transaction txn)
at Microsoft.SharePoint.Workflow.SPPendingWorkBatch.Commit(Transaction transaction, ICollection items)
03/14/2014 12:30:30.05    w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          88xr   Unexpected   WinWF Internal Error, terminating workflow Id# 2dc6002d-9f9d-474f-84cf-329025347ec5
03/14/2014 12:30:30.05    w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          98d4   Unexpected   System.Workflow.Runtime.Hosting.PersistenceException: This task is currently locked by a running workflow
and cannot be edited. ---> Microsoft.SharePoint.SPException: This task is currently locked by a running workflow and cannot be edited.     at Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, SPWeb web, Boolean
bMigration, Boolean& bAdd, Boolean& bPublish, Object& objAttachmentNames, Object& objAttachmentContents, Int32& parentFolderId)     at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion,
Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean suppressAfterEvents)     at Microsoft.SharePoint.SPListItem.Update()     at Microsoft.SharePoint.Workflow.SPWi...
03/14/2014 12:30:30.05*   w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          98d4   Unexpected   ...nOEWSSService.CommitUpdateListItem(Transaction txn, Object[] transData)     at
Microsoft.SharePoint.Workflow.SPPendingWork.PerformWorkNow(Transaction txn)     at Microsoft.SharePoint.Workflow.SPPendingWorkBatch.Commit(Transaction transaction, ICollection items)     at System.Workflow.Runtime.WorkBatch.PendingWorkCollection.Commit(Transaction
transaction)     at System.Workflow.Runtime.WorkBatch.Commit(Transaction transaction)     at System.Workflow.Runtime.Hosting.WorkflowCommitWorkBatchService.CommitWorkBatch(CommitWorkBatchCallback commitWorkBatchCallback)
at System.Workflow.Runtime.Hosting.DefaultWorkflowCommitWorkBatchService.CommitWorkBatch(CommitWorkBatchCallback commitWorkBatchCallback)     at System.Workflow.Runtime.WorkflowExecutor.CommitTransaction(Activity activityContext)
03/14/2014 12:30:30.05*   w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          98d4   Unexpected   ...   at System.Workflow.Runtime.WorkflowExecutor.Persist(Activity dynamicActivity, Boolean
unlock, Boolean needsCompensation)     --- End of inner exception stack trace ---     at System.Workflow.Runtime.WorkflowExecutor.Persist(Activity dynamicActivity, Boolean unlock, Boolean needsCompensation)
at System.Workflow.Runtime.WorkflowExecutor.System.Workflow.ComponentModel.IWorkflowCoreRuntime.PersistInstanceState(Activity activity)     at System.Workflow.ComponentModel.Activity.MarkClosed()     at System.Workflow.ComponentModel.Activity.ReleaseLockOnStatusChange(IActivityEventListener`1
eventListener)     at System.Workflow.ComponentModel.FaultAndCancellationHandlingFilter.SafeReleaseLockOnStatusChange(ActivityExecutionContext context)     at System.Workflow.ComponentModel.FaultAndCancella...
03/14/2014 12:30:30.05*   w3wp.exe (0x7698)                          0x7A94   Windows SharePoint Services
    Workflow Infrastructure          98d4   Unexpected   ...tionHandlingFilter.OnEvent(Object sender, ActivityExecutionStatusChangedEventArgs e)
at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)     at System.Workflow.Runtime.Scheduler.Run()
03/14/2014 12:30:30.38    w3wp.exe (0x7698)                          0x6C9C   Windows SharePoint Services
    General                          0   Unexpected   ERROR: request not found
in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 59, Free call stack =    at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request)     at Microsoft.SharePoint.SPWeb.Invalidate()
at Microsoft.SharePoint.SPWeb.Close()     at Microsoft.SharePoint.SPSite.Close()     at Microsoft.SharePoint.SPSite.Dispose()     at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflow(SPWorkflow
workflow, Collection`1 events, SPRunWorkflowOptions runOptions)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflow(SPWorkflow workflow, Collection`1 events)     at Microsoft.SharePoint.Workflow.SPWinOEItemEventReceiver.RouteWorkflowEvent(SPItemEventProperties
properties, SPWeb web, SPListItem item, Boolean fNeedTas...
03/14/2014 12:30:30.38*   w3wp.exe (0x7698)                          0x6C9C   Windows SharePoint Services
    General                          0   Unexpected   ...kReset)
at Microsoft.SharePoint.Workflow.SPWinOEItemEventReceiver.ItemUpdated(SPItemEventProperties properties)     at Microsoft.SharePoint.SPEventManager.RunItemEventReceiver(SPItemEventReceiver receiver, SPItemEventProperties properties, SPEventContext
context, String receiverData)     at Microsoft.SharePoint.SPEventManager.RunItemEventReceiverHelper(Object receiver, Object properties, SPEventContext context, String receiverData)     at Microsoft.SharePoint.SPEventManager.<>c__DisplayClass8`1.<InvokeEventReceivers>b__0()
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)     at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)     at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken
03/14/2014 12:30:30.38*   w3wp.exe (0x7698)                          0x6C9C   Windows SharePoint Services
    General                          0   Unexpected   ...userToken, CodeToRunElevated
code)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](SPUserToken userToken, RunEventReceiver runEventReceiver, Object receivers, Object properties, Boolean checkCancel)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](Byte[]
userTokenBytes, RunEventReceiver runEventReceiver, Object receivers, Object properties, Boolean checkCancel)     at Microsoft.SharePoint.SPEventManager.HandleEventCallback[ReceiverType,PropertiesType](Object callbackData)
at Microsoft.SharePoint.Utilities.SPThreadPool.WaitCallbackWrapper(Object state)     at System.Threading.ExecutionContext.runTryCode(Object userData)     at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
code, CleanupCo...
03/14/2014 12:30:30.38*   w3wp.exe (0x7698)                          0x6C9C   Windows SharePoint Services
    General                          0   Unexpected   ...de backoutCode, Object
userData)     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)     at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback
tpWaitCallBack)     at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state) , Allocation call stack (if present) null

Error Handling on OM Workflow.

Hi Guys, I have a question.
I have a requirement on OM sales order form, suppose an workflow errors out because of some missing data. If the users enters or corrects the data, Now he want the workflow to start by some action on form instead of waiting for sysadmin to do retry. he is asking because there might be a chance of delay by sysadmin in doing retry. I am wondering whether this is possible on the form. If possible, can someone suggest me a way to do that.
Thanks in advance.

HI Rick,
Thanks for your Inputs.
Still i am in Confusing with word " Temporary" . I have Defined Exception for my method as you suggested. But i have not found any check box or option in method to choose for temp. Please tell me where i have to choose it as Temporary.
Or else If write just "exit_return 9006", will it consider as Temporary error.
Waiting for your inputs.
Regards, Sri harsha.

Workflow Error Purchase Order

Hi Experts,
my issue is the following: We try to create a purchase order in SRM with a local mapped category (mapped to the local srm system) and depending on the user the target system should be overwritten in BADI bbp_determine_logsys to get the purchase order in the respective backend.
The idea is to use all categories centrally and map them depending on the purchasers origin country.
The question is that ...
If we map the category to the backend system of the purchaser and try to transfer the purchase order, there will be no error (not in RZ20 or anything) - of course also the direct way with the FU bbp_procdoc_tansfer will work.
If we map the category as it should be to the local srm system - the workflow transfer won't work anymore and we got an error message in RZ20 with the following text: Error reading the export data for EXEC transfer of purchase order <PO No.>.
The very strange thing is, that even in this case with the FU bbp_procdoc_transfer the purchase order can be transferred to the backend of the respective user and it will switch the locally mapped backend to the purchaser / users one.
Could anyone imagine what might be a problem - is there any check in the workflow itself what raises the exception and aborts the workflow.
Thanks for your help.
Cheers,
Timo

I am not sure if this is gonna help you..
Note 1154122 - BBP_POC : Backend Data validation from SRM
Regards,
PR.

Error Handling for Background/Update Tasks (Transfer Order creation) - How?

Hi,
I have a standard process for creating a Transfer Order and 2 user-exits that I have implemented.
The user exits are used to transfer information during Transfer Order creation.
However, the user-exits also check data in table TVARV and other. As such, error handling needs to be implemented, since the T.O. might or might not go through, depending on data validation and related.
However, the user-exits are implemented during creation, which is an update task that runs in the background. This makes it impossible to output any information or error messages.
What else can be done in regards to outputting a message, since the user will need to see some sort of message that the process failed, that the T.O. didnu2019t confirm? Can an SAP inbox message be created and how?
Please help.
Thank You,
John

Hi,
Please check the following link for all the function modules and user exits on TOs.
http://help.sap.com/saphelp_erp2005/helpdata/EN/c6/f83a294afa11d182b90000e829fbfe/content.htm
Reward points if it was helpful.
Regards
Abhishek
Edited by: Abhishek Raj on May 29, 2008 10:20 AM

Can error handling framework use fault policies and BPEL catch blocks

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

Error handling workflow not getting triggered

Hi all,
I'm creating a outbound IDoc. And for error handling workflow.. I created a organization structure in PPOME and assigned users. I gave this position number thus created in the partner profile in post processing permitted agent tab.
But when the Idoc is in error, this is not coming to my inbox.
Can someone please help me with this.. and let me know what went wrong.
Thanks in advance.

Here you need to be careful,
if the agent assignment is not maintained properly, there may be a chance everyone in the organization will get the item.
I hope you have created a single workitem for error handling. goto additional data-> agent assignment-> maintain. make sure the attribute is defined as general forwarding allowed. or you maintain the role/position/user/whatever.as the possible agents. still you dont get the result, debugging the default rule in the task ->default rule -> agent.
hope this helps.
with regards,
Sudhahar R

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi 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.

IDoc error handling using workflows

Hi,
I have a requirement to generate IDocs in the Source system and process them in the target system. The IDoc message type is HRMD_ABA. And I am using standard processes to generate them and post them using PFAL and RBDAPP01 program respectively.
All this is working fine. But now I need to include error handling in the source and the target systems which would send mails to a User's Outlook mailbox whenever there is an error. I mean to say, we need more functionality than just monitor them through WE05 transaction.
Can any one tell me how this can be achieved. I have been looking into the program RSEIDOCA which would send workflows to SAP Inbox, but I need to send it to Outlook Inbox.
And I have heard that there is a workflow process which would help me to do this.
All your answers would be highly appreciated.
Thank you in advance,
Sid.

Hi,
First Step:
You have to maintain the e-mail-address in SU01 for required users.
Second Step:
SCOT Configuration
Third Step:
Depends on your SAP Version do configuration SWNADMIN
Or excuting the report RSWUWFML2 as the background job.
Thanks and Regards,
Prabhakar Dharmala

VS Workflow - Erroring out when multiple records are created by same user

Hi,
I am using SP 2013. I have a visual webpart and custom sequential workflow. The webpart saves the data to a custom list and the workflow is associated to the custom list on Item creation only. In the workflow, I am breaking the role inheritance and setting
permission to specific set of users, and then the normal approval workflow happens. The whole workflow condition works fine, but if the user is raising multiple requests one after another, the workflow seems to break either in the Break inheritance or granting
permission. If the user raises only one or two requests then everything works fine.
Below are the errors which I am getting in the workflow:
Error 1:
Error: Save Conflict. Your changes conflict with those made concurrently
by another user. If you want your changes to be applied, click Back in your Web
browser, refresh the page, and resubmit your changes.
I have already checked this :
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/60ab04fd-9650-427d-a48f-784bc22fae05/workflow-and-save-conflict-your-changes-conflict-with-those-made-concurrently-by-another-user?forum=sharepointdevelopmentprevious_
http://adrianhenke.wordpress.com/2010/08/20/sharepoint-error-save-conflict-your-changes-conflict-with-those-made-concurrently-by-another-user/
I have also implemented the "Reload" thing posted in the above URL. This error only happens when multiple new requests are getting raised by same user. This error does not happen if I terminate the workflow and re-start the workflow.
How to fix this?
Thanks

Hi,
Based on my understanding, you have a Visual Web Part for adding new item into a list. A workflow will be triggered when item creation in this list. Everything works
fine except when an user adds multiple items in a short period.
If this is the case, plus with the error message, a possible cause is that the SharePoint Server and the workflow engine are not functioning effectively enough to
handle the multiple request in a short time, therefore a scenario is that when there is new item being added into the database, the workflow modifies the “RoleAssignments” property of this item at the same time, this may cause a “Save Conflict” error.
As you said, “If the user raises only one or two requests then everything works fine”, a workaround is that you can disable the adding item function in Visual Web
Part forcibly in a specific period after a new item is being added by current user, it can leave some time for handling the item creation and item modification.
Or if there is a need to submit multiple items concurrently, we can organize the requests into one request, then handle this item with other custom logic in your workflow.
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Patrick Liang
TechNet Community Support

Error 'Handling unit was not blocked - action cancelled' for Packing

Hi Friends
I am trying to execute Functional Module HU_PACKING_AND_UNPACKING to Pack Sales Order Line Items in to HU.
But System is throwing unusual error Handling unit was not blocked - action cancelled
The Other SAP SDN thread advised to implement OSS Note 370195 , 331715.
The Input Code given in the Note 370195 SAP Developer can not find in our system.
SAP Note 331715 already implemented in our system.
Please help to resolve the issue for Packing Sales Order Line Items in to HU.
Thanks
SR

Refer OSS Note 370195 , 331715

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

Error handling of Assignments in Workflow...

Hi All,
How we do we automate assignment's error handling in Workflow.
For example: I have an assignment and that is part of my workflow.
If the assignment fails the workflow job status gets "Error" status --> How do we handle this by sending some notification or branch into success or failure?
Please feel free to revert to me.
thanks
Alexander.

Hi Alexander,
MDM Assignment is not like Validation based on which you can branch out your process based on the validation result.
Assignment will assign a value to the desired field based on the expression you write.
So you need to take care that your expression handles all the incoming records fully and does not fail.
Hope It Helped
Thanks & Regards
Simona Pinto

Order blocked by user / Workflow error handling

Similar Messages

Maybe you are looking for