Workitem in process

HI ALL,
i have developed custom workflow to execute HR training process.it has three level approval.
1. supervisor
2. hod.
3. HR department
i have used custom screen for each approval process.....it working fine in developement system.....
but when i executed same workflow in TST system for supervisor i can able to execute workitem...
when i clicked on HOD work item it taking more time and going to dump.....
before dump i checked authorization level.i got below message.
authorization check failed.
authorization object: S_WF_WI
classification of task:   NO_CLASS
activities for authorization check:      19
Work item type:     W
S_WF_WI has more functionality. but i want give authorization to execute work item only...
do you have any idea....

problem not yet solved...i am facing new problem.
when i tried to execute methods from SWO1 for standard object PDRELA_025 as well as subtype.it taking more time, then going to dump ( time out error).i have checked dump file.in the place taking more time while fetching the value from table HRP1001 and it goes for dump.
when i execute work item in same person inbox also going to dump.
this problem rising for specific user id.
kindly suggest your solution.
thanks in advance.
regards,
ram
Edited by: Raja Ram on Jul 21, 2009 1:40 PM

Similar Messages

How to set the status of an Workitem, while processing?

Hi,
My requirement is to set/ Change the workitem status after/ while procecssing if certain condition is not met for all the users. I have one workitem assigned to multiple users. If any one of the user's executes the workitem, it displays a zprogram, but the user has not taken any action (SAVE), he simply came out of the transaction using "BACK" button. Here the Workitem has been vanished/disappeared from the other two users Inbox, and the workitem is in "In Processu201D Status for the User who executed the workitem. But my requirement is to set the workitem to be in "READY" status for all the users to whom the workitem is assigned; until the user "SAVE" the transaction I need the workitems to be in "READY" status only.
Please suggest me with your ideas to get the above results.
Note: I have used the function modules u201CSAP_WAPI_SET_WORKITEM_STATUS (or) SWW_WI_ADMIN_READY ", to change the status of the workitem while processing, it's throwing an error u201CWork item & locked by user & (enqueue erroru201D.
Thanks in advance,
Ajay Kumar

Thanks Florin,
Your piece of code has worked alot, and it was very helpful in changing the Status of the Workitem to "READY" for all the Users fo the workitem.
Points have been rewarded for your help.
Process: We have acheived this using the "Work Item Exits", Usng "AFTER_EXECUTION" Method.
Note: The Exit will be executed if "exit_cancelled" statement is present/used in the work item method. if not it is not taking to the exit code. I'm unable to find the reason for it. Florin can u please explain this point.
Please check the link for adding the code in Work Item Exits.
http://wiki.sdn.sap.com/wiki/display/ABAP/ProgramExitsIn+Workflow
Please find the Code:
method IF_SWF_IFS_WORKITEM_EXIT~EVENT_RAISED.
Get the context of the workitem
me->wi_context = im_workitem_context.
After execution of the workitem call the method AFTER_EXECUTION
if im_event_name eq swrco_event_after_execution.
    me->after_execution( ).
endif.
endmethod.
METHOD AFTER_EXECUTION.
This method acts as the Event Handler for SWRCO_EVENT_AFTER_EXECUTION
DATA: LCL_L_WID TYPE SWW_WIID,
        L_STATUS TYPE SWR_WISTAT-STATUS,
        L_NEW_STATUS TYPE SWR_WISTAT,
        L_SWR_MESSAG TYPE STANDARD TABLE OF SWR_MESSAG,
        L_SWR_MSTRUC TYPE STANDARD TABLE OF SWR_MSTRUC.
Get work item
CALL METHOD WI_CONTEXT->GET_WORKITEM_ID
    RECEIVING
      RE_WORKITEM = LCL_L_WID.
L_STATUS = 'READY'.
CALL FUNCTION 'SAP_WAPI_SET_WORKITEM_STATUS'
    EXPORTING
      WORKITEM_ID    = LCL_L_WID
      STATUS         = L_STATUS
      USER           = SY-UNAME
      LANGUAGE       = SY-LANGU
      DO_COMMIT      = 'X'
    IMPORTING
      NEW_STATUS     = L_NEW_STATUS
     RETURN_CODE    = SY-SUBRC
    TABLES
      MESSAGE_LINES = L_SWR_MESSAG
      MESSAGE_STRUCT = L_SWR_MSTRUC.
IF SY-SUBRC EQ 0.
ENDIF.
ENDMETHOD.
Thank You Once Again,
Ajay Kumar Chippa

Batch Processing for Workitem - Result Processing

Hi All,
I'm having problem in a workflow step.
When the workflow step is execuetd i'm getting a step log as:
Batch Processing for Workitem     Dialog work item created          14.05.2009 09:09:59
user01                    Execution started               18.05.2009 05:57:18
user01                    Work Item Processing Complete     18.05.2009 06:04:46 Functionality for Hi 000600113419
user01                    Terminating event received          18.05.2009 06:04:46 Functionality for Hi 000600113419
Batch Processing for Workitem     Result Processing               18.05.2009 06:04:46
Can any one please let me know what code/program is executed in *Result Processing *

I read this in the documentation:
If necessary, the G/L account can also be set so that the tax code is not a required entry when posting transactions not relevant to tax
How would I set this?? Or where is it done?

Can we set "IN PROCESS" Status to more than one User

Hi,
As per my client current scenario every work item will be sent to 3 useru2019s (One is the supervisor of the other two users). If any one of the user executes the work item it will automatically call a Ztransaction and displays the screen. When any one of the user executes the workitem, then the workitems will dissappears from rest of the users inboxes; Setting "IN PROCESS" status for the person who executed the workitem. The workitem will be in "IN PROCESS" Status untill the User Press "SAVE" button in the transaction.
If the person whose executed the workitem (IN PROCESS) status, has gone on unplanned leave; then the supervisor wants to forward the workitem of the current user to other user. How can he forward?
Is there any option to set "In Process" status to more than one User? [Supervisor and Person who executed the workitem]
Please provide me any advice to the above requirement.
Thanks in advance,
Ajay Kumar

Can you ask your workflow administrator to forward the workitem to the user you want to be sent it to.
I tried a small case wherein I had forwarded a workitem to myself and another user.
As I executed it , it went into status IN process and at the same time it got removed from other users inbox .
Now I went to T Code SWI1 and forwarded iut to another user say USABC.
As a result the workitem again went into status "Ready" and into the inbox of the user ABC.
So , you can try this in your case with the help of your workflow administrator.
Another way is to create the other user as a substitue of the user who is currently executing the workitem.

Asynchronous task workitem

Hi ,
I have defined a terminating event " PROCESSED" for element "_WORKITEM " in "Terminating events" tab of task definition.
when ever my Asynchronous task workitem is opened and closed without procesing, the workitem disappears from
SAP Inbox .
but the wokitem should be in inbox until the workitem is processed ( that means invoice gets posted from workitem ).
please let me know the solution to resolve this issue.
Note : only the folllowing terminating events availble . a) Processed b) created c) Deleted for element "_WORKITEM "
Thanks ,
Sarath.

Hi Sarath,
I have used follwing setting for terminating event used in a task
Element : WIOBJECT_ID
Object Category :ABAP Class
Object Type :ZITEM
Event : APPROVED
This works for me.
Please check "Synchronous Object Mehod " must not be checked in Basic data tab of tha task.
Thanks and regards,
SNJY

Workflow completing on Deleted event but workitem still active

I have a couple of different FI workflows with forks with 3 branches...1 being necessary. One branch is approval and the other two are change and deleted events which should completed workflow if either are raised. Both of them are basically the same layout:
These workflows have only recently started having problems. Sometimes when the deleted event is raised, the workflow is completed but the approval workitem remains in process in the users inbox:
I checked the transaction log and some work and some do not. I looked in ST22 but didnt see any errors that look related. Looking through the workflow log itself, everything seems normal except the approval workitem doesnt logically delete when the workflow is completed. I also looked at any execution times that might coincide with the document delete time and didnt really see anything that might point to an enqueue problem.
Has anyone else experienced anything like this?
*edit I looked a little further back into the log and it appears that in each instance that it didnt work, the approver had the workitem in process at the time of the deletion.

The deleted event was raised 7/22 at 9:50
The approval workitem was executed and canceled and the restarted just prior to that:
I havent been able to re-create this problem in test system no.

BPM message is being sent

Hi,
i put two receive step in fork step and two send step.
two receive step has start point, when both two step are received, one receive step will be sent to legacy and then another receive step wil be sent to legacy. if one of receive step is not received, send step should not be activated.
my problem, when two receive step were received, send step does not work, in sxmb_moni, i can see this "message is being sent".
what did i have wrong step?
thanks
venjamin

Hi,
Hope you have proper correlation set up in the BPM.
Go to Technical Details of the BPM to get the more info.
( SXMB_MONI->PE->Technical Details)
just cross check with BPMPatterns in the SAP BASIS software component.
http://help.sap.com/saphelp_nw2004s/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0e/56373f7853494fe10000000a114084/content.htm
>>>just go to SWWL transaction and delete all the error workitems and process once again..
Hope this helps,
Regards,
Moorthy

Bad expiration date

I have created a BPEL process with wait activity, there are input for process start time (datetime) and interval(duration). while creating an instance(workitem) in process, it moves to wait and on console i got the error
<Mar 23, 2011 9:27:53 PM SGT> <Error> <oracle.soa.bpel.engine.bpel> <BEA-000000>
<<BPELReceiveWMP::__defineExpirationDate> Bad expiration date format, and this
expiration date will be ignored
java.lang.IllegalArgumentException: Duration has to start with 'P'.
Input payload for process is:
<inputVariable>
<part name="payload">
<ns1:process>
<ns1:startDate>2011-03-23T16:30:00.000+08:00</ns1:startDate>
<ns1:interval>PT2M</ns1:interval>
</ns1:process>
</part>
</inputVariable>
And in wait have putted
string(bpws:getVariableData('inputVariable','payload','/client:process/client:startDate'))expression in "for" column
*WaitForStart (pending)
Mar 23, 2011 9:27:53 PM Bad expiration date "2011-03-23T16:30:00.000+08:00"
Mar 23, 2011 9:27:53 PM Waiting for the expiry time "never".*
environment is:
SOA 11.1.1.3.0
Jdeveloper: 11.3

I kept watching this forum for an answer and noticed one item where the user indicated that after a failure repeated attempts to clean and align heads 'magically' worked. I had not used the printer for a week and decided to give it one more try. It worked. The printer is just fine after sitting idle for a week and then trying the clean followed by align. It would still be interesting to understand why. I'm glad I didn't run out to buy more cartridges and throw this one out.

Workflow Dialog Issue

Hi everybody,
I have created a WF with 4 user decisions. One of the user decisions is Display PO which should call the transaction ME23N. I have created the method associated to the task as Synchronus and Dialog. And in Task, I made the task as general task and in WF I have done the agent assignment.
The issue is when user selects the option Display PO instead of calling the transaction the workitem gets processed and disappears from the inbox. User is not at all able to see the PO.
And also when I see the WF log, I see an error message 'EVALUATE_AGENT_VIA_EXPESSION'.
Could anyone please help me and let me know what could be the possible reason?
Thanks,
Murali Krishna Kovur.

Hi Abhishek,
Yes, My workitem is going to the right place.
I have tested the method associated with the Display PO task, independently and it is working fine.
I am passing the position of the user who actually process the Workitem as Agent to the task in WF.
Is there anything missing?

Custom Event In DMS

Hi,
I have a requirement where in a document need to be digitally signed/approved - parallelly ( say by 3 people - par for each).
The object is DRAW and the method is EDIT. The terminating event for this step is event CHANGED.
Now the problem is: when ever the first person signs the document this step gets completed with out others being able to sign.
How can this problem be solved - should i create a custom event? Please explain in detail. Points Guaranteed !!!
Regards,
Venkat.

Hi Venkat,
Workflow triggers here and routes it to 3 approvers.
From this i understand that you have three activity steps in parallel using a fork. Right? Or do u mean to say the same workitem has three agents and is delivered to three peoples inbox. If you are delivering the same work item to three inboxes there is no way that you can have it in other agents inboxes after being processed by one agent. In fact immediately after the first agent opens the workitem for processing it will disappear from the inbox of other agents.
But if you are using three steps in parallel under a fork. Yes you can achieve this.
Section 1:
You have already created a ZEDIT method and made the method as synchronous. Hence you must have made the task also as synchronous (checkbox "Synchronous object method" checked). Now goto the "Terminating Events" tab of the task. If you still have the terminating event here just delete it. You will not need this as your workitem will get automatically completed when the BO method is executed once.
Now assign this task to the three activities (for three agents) under the fork step. Now when a workitem is created for this task you will get the workitems in all three inboxes (These will be three individual workitems belonging to each activity inside the fork). Now each of these workitems are independent of each other and will not affect other workitems based on its own processing status.

Section 2:
If you have reached till above your approvers will be able to process the workitem independent of each other. Now again you will have a problem here. Once you have made your task as synchronous it just waits for the execution of the BO method and it does not know whether you have achieved the purpose of the method. In your case your objective is to edit the document. But if your approver executes the workitem once it will bring him to CV02N. Now assume he wants to edit the document later and he presses the "BACK" button. Your objective is not completed but still your BO method will get completed and hence terminate the workitem of that approver. To avoid this you need to get back the sy-ucomm value for BACK into your BO method and write a few lines of code such that your workitem will not get terminated when BACK is pressed. This can be done using some BADI's available for this transaction.
Thanks,
Prasath N

UWL custom view

I'm not an espert by any means in this area but I am trying to add a custom view to the UWL with approve and reject buttons so the user does not have to open each workitem to process them. I have managed to get the subview to appear on the UWL but no workitems are in the list despite there being some in the main view. I have put the XML code below, anyone have any ideas what is wrong with it?
Thanks
Rob
Code:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE UWLConfiguration (View Source for full doctype...)>
- <UWLConfiguration version="1.0">
- <ItemTypes>
- <ItemType name="uwl.task.webflow.decision.TS92000003.Finance_and_HR" connector="WebFlowConnector" defaultView="myApprovalView" defaultAction="viewDetail" executionMode="default">
<ItemTypeCriteria systemId="Finance_and_HR" externalType="TS92000003" connector="WebFlowConnector" />
- <Actions>
- <Action name="Approve" groupAction="yes" handler="UserDecisionHandler" returnToDetailViewAllowed="yes" launchInNewWindow="no" defaultGroupAction="no">
<Descriptions default="Approve" />
</Action>
- <Action name="Reject" groupAction="yes" handler="UserDecisionHandler" returnToDetailViewAllowed="yes" launchInNewWindow="no" defaultGroupAction="no">
<Descriptions default="Reject" />
</Action>
</Actions>
</ItemType>
</ItemTypes>
- <Views>
- <View name="myApprovalView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.webflow.TS92000003" columnOrder="statusIcon, subject, creatorID, createdDate, dueDate, priority, approveCol, rejectCol" sortby="createdDate:descend, priority:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="yes" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="-1" dueDateSevere="0" dueDateWarning="0" emphasizedItems="unread" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="bottom" tableNavigationHeaderVisible="no">
- <Descriptions default="Application Mass Approval">
- <ShortDescriptions>
<Description Language="en" Description="Application Approval" />
</ShortDescriptions>
</Descriptions>
- <DisplayAttributes>
- <DisplayAttribute name="rejectCol" type="checkbox" width="" sortable="no" format="default" actionRef="2" hAlign="CENTER" vAlign="TOP" maxTextWidth="0" headerVisible="yes">
- <Descriptions default="">
- <ShortDescriptions>
<Description Language="en" Description="Reject" />
</ShortDescriptions>
- <LongDescriptions>
<Description Language="en" Description="Reject the request" />
</LongDescriptions>
</Descriptions>
</DisplayAttribute>
- <DisplayAttribute name="approveCol" type="checkbox" width="" sortable="no" format="default" actionRef="1" hAlign="CENTER" vAlign="TOP" maxTextWidth="0" headerVisible="yes">
- <Descriptions default="">
- <ShortDescriptions>
<Description Language="en" Description="Approve" />
</ShortDescriptions>
- <LongDescriptions>
<Description Language="en" Description="Approve the request" />
</LongDescriptions>
</Descriptions>
</DisplayAttribute>
</DisplayAttributes>
- <Actions>
- <Action name="1" groupAction="yes" handler="UserDecisionHandler" returnToDetailViewAllowed="yes" launchInNewWindow="no" defaultGroupAction="no">
<Descriptions default="1" />
</Action>
- <Action name="2" groupAction="yes" handler="UserDecisionHandler" returnToDetailViewAllowed="yes" launchInNewWindow="no" defaultGroupAction="no">
<Descriptions default="2" />
</Action>
<Action reference="submitUserDecisions" defaultGroupAction="no" returnToDetailViewAllowed="yes" launchInNewWindow="no" />
</Actions>
</View>
</Views>
</UWLConfiguration>

Hi,
Check this blog may be usefull.
Flashy UWL ...
Complete customization of UWL UI.
Thanks and Regards,
gopal

Steps for Idoc to EDI Subsystem

Hi all,
Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
I mean what all things i have to specify while creating ports and partner profiles etc
Thanks

Sending Order Confirmations by EDI (SD-SLS)
Use
By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
Prerequisites
Application
Customizing
To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
Output Control
The standard SD condition components are:
Condition component     Value
Sales document type     AA
Output determination procedure     V10000
Condition type     BA00
Transmission medium     6 (EDI)
Access sequence     0001
Processing subroutine     Program RSNASTED, form routine EDI_PROCESSING
Partner function     SP (sold-to party)
Application     V1
Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions  Output Control  Output Determination  Output Determination Using the Condition Technique  Maintain Output Determination for Sales Documents.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
Field     Value
Message type     ORDRSP
Partner type     KU (customer)
Partner function     SP (sold-to party)
Receiver port     e.g. SUBSYSTEM
Output mode     e.g. Transfer IDoc immediately
Basic type     ORDERS04
Process code     SD10
Activities
Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras  Output  Header.
Receiving Acknowledgments via EDI (MM-PUR-GF-CON)
Use
You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
Prerequisites
Application
To work with several categories of vendor confirmation, you must:
u2022     Enter a confirmation control key on the item detail screen
u2022     Set up the confirmation control facility in Customizing for Purchasing (Purchasing  Confirmations  Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
Under Confirmation sequence, you can:
u2022     Specify tolerances for date and price checks
u2022     Allow vendor material changes (VMat indicator)
u2022     Adopt vendor price changes (Price indicator)
Do not use a confirmation control key if you work exclusively with acknowledgments.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  EDI  Set up Partner Profile):
Parameters for Inbound Messages
Field     Value
Partner type     LI
Partner role     LF
Message category     ORDRSP
Process code     ORDR
Processing     Initiate immediately or process via background program
Activities
When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
u2022     If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
u2022     If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item  Confirmations  Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
Exceptions
When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
Sending PO Change Notices via EDI (MM-PUR-PO)
Use
This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
The function corresponds to the transmission of a purchase order via EDI.
Prerequisites
Application
You have already successfully transmitted the original purchase order to the vendor via EDI.
Message Control
You have created message condition records for your EDI vendors (Purchasing  Master data  Messages  Purchase order  Create).
Use the message type NEU to transmit PO change notices.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  Set up Partner Profile):
Parameters for Outbound Messages
Field     Value
Application     EF ( Purchasing: purchase order)
Message category     ORDCHG
IDoc type     ORDERS02 or ORDERS04
Process code     ME 11 (ORDCHG: PO change notice)
If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
Activities
Change an existing purchase order via Purchasing  Purchase order  Change. Make the necessary changes and save the PO.
The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header  Messages in the PO item overview.
See also:
MM Purchasing: Creating a Purchase Order
Cross-Application Components: Customizing Message Control in Purchasing (MM): Example: Purchase Order
Receiving Order Changes by EDI (SD-SLS)
Use
In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
Prerequisites
Application
General
You can receive and process order changes in your system only on the basis of an existing order.
Customizing
To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
Parameter     Value
Partner type     KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
Message type     ORDCHG
Process code     ORDC
Processing     Process immediately
Allowed Agents     Enter an R/3 user or an organizational unit, for example.
Activities
Inbound Processing
The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
Exception Handling
If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
To display an IDoc for order changes, choose Environment  Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs.

Workflow-No agent

Hi ,
I have a workflow wherein the status in SWI2_FREQ is appearing as 'No Agent Available' and status as 'Ready'. But the "Agent" is able to see it in his inbox. Once the Agent processes the work item it shows up under his name in SWI2_FREQ as completed. Why is that the task appears as "No agent found" though clearly it has been able to resolve an agent? Is it that unless the workitem is processed it will remain in that state?
Regards,
Hari.

Hi Hari,
Could you please check, whether the Dialog task that has been defined is a Standard task or not. This can be checked by
1. Go to Transaction PFTC
2. Give the task name, go in Change (F6) Mode.
3. From the Menu bar, Additional Data -> Agent Assignment -> Maintain.
4. Click on the name, then on Attributes, Click on the General Task RadioButton
Please, let me know if further details are required.
Regards,
Goutham.

TS20000159 after Complition Not Going in Outcome -Rejected

Hi All,
I am working on PR Workflow . Here I used the Task TS20000159 . After creation of PR , the workitem comes in the approvers inbox . When the Approver processes the workitem , the process flow doesnt go into any of the task outcome . Infact it gets strucked here . In Workflow Graphical display , shows green line till this task only .
One more thing this task doesnt disapper from the approver inbox even after processing .
Any idea why this is happening ???
Thanks
MD

hi,
may be u can check for the following things:-
1> the binding b/w the task and the WF
2> the "confirm end of processing has been checked" in transcation PFTC.
in the log, go to the technica details and check the container elements , may b there u wll come to know about the exact issue..!!
please let me know if it helps u
regards
kanika

UWL work items

Hi,
There are UWL work items and when a user selects a workitem to process, UWL opens up a new window when you choose an item.
It should go to the item in same window and when complete take you back to the UWL, where the item completed should no longer display in the list.
Please advice further - Thanks
Regards, Neeta

Hi ,
check the below thread.
download standard uwl configuration xml file and check the property related to newwindow feauture and set it to false.
then it will open in same window rather than new window
check example code in that which used to open in new window
UWL - open item in new window
Koti Reddy

Workitem in process

Similar Messages

Maybe you are looking for