Error in PR standard workflow WS20000077

Hi Friends ,
I have activated the standard workflow WS20000077 which is for PR release procedures . When i am creating a PR it is triggering the workflow with an error " Import container contains errors (are any obligatory elements missing?) " .
I have checked the forum for the same error but i did not find ant exact solution for that .
In SWEL , the object key is being populated by the PR no . So i think this is the problem due to the Release code which is not getting any value in the event container after the event " Releasestep craeted" gets triggered .
So please guide me on the same how to resolve the above error .
I am using ECC 6 version of SAP .
Thanks in advance
Sarmistha

Thanks again for your reply .
I have tested the workflow in SWUE by assigning the Release code value manually and the workflow is triggering without any error .
So as you told i think some SAP Notes needs to be implemented to resolve this issue .
If you have any idea on this please guide .
Thanks
Sarmistha

Similar Messages

Additional PR release step while using standard workflow WS20000077

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. Release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the 1st release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise is it possible and how to implement the additional release step. Thanks.

Thanks for your quick response.
I also think about this to keep workflow side untouch by including one additional release code in MM release strategy configuration. Unfortunately material group is item-wise, material group of item 1 may not be the same as item 2 (unless we restrict all items' material group to be identical by user-exit). Otherwise, I'm not sure how to incorporate this into a document level overall release strategy.

Error in SAP standard workflow ddoStart - Start document distribution

Hi all,
I'm trying to use the document distribution but i'm failing completely. After doing what i think is the necessary config (setting all relevant tasks to general task should be all), i try to distribute. I create a list, selects people and click go.
When checking the log for the distribution later on, all workflows generated hang in the same place - namely the case branch before "check document distribution". Further on, the "check distribution order" task does have three potential outcomes after calling the business objects corresponding method. The problem is that the method "check" of bus1082 (doc. dist. order) does not return a check value as a parameter, even though it has a result internally.
I suspec i'm missing something here, but the wf still bombs out.
Tips and tricks guys?
Espen

HI all,
Problem is identified and a solution is found. THe businesss object's methods for distribution order did not have the flag for result parameter ticked. Opening up the standard SAP objects, tick the box and voila - it works.
Still puzzles me how SAP did release this. Didnt they test?
Espen

PR Release Workflow WS20000077

Hi Workflow Gurus,
I am using SAP provided standard workflow (WS20000077)for PR Release. This workflow is triggered when event Release step generated is raised in the system.
I have PR with two release code L1 and L2. If i see the workflow it has only one level.
My question is that is it necessary to add another level insiade my workflow?
or
When level one (L1) releases,current workflow will be completed with L1 release and agin workflow will be triggered for the same PR with release code L2.
Please help.
Thanks in advance.
Regard
Sagar

Hi Sagar,
If it is value based, then u need to create characteristics for price value and include that characteristics in class and then use that class in release strategy. And u need to give the range of value in Classifications in Release Strategy. you can refer the following link for release strategy,
http://help.sap.com/saphelp_47x200/helpdata/en/04/92761846f311d189470000e829fbbd/frameset.htm
Regards,
JMB

Information message to Error Message -HCM standard Leave Workflow

Hi ,
I am configuring leave management for a demo purpose.
The leave application workflow used is ws20000081.
There are few scenarios configured in system for not allowing leave applications for the employees .
Example:-paternity leave u2013 maximum days which employee can apply through one application is 3 working days
This validation is working fine as we directly using IT2001 application through tcode- PA30 .more than 3 days it giving an error message.
But issue is
When we are applying the leave through ws20000081, system is allowing more than 3 working days and allows a successful application. Then its allows a successful approval for employer. After approval system fails to update the data in system and forward the application to administrator where as in ideally system should not be allowing the employee for a successful application.
When we are applying the leave through ws20000081 and clicking on the u201Cchecku201D button system is giving the actual error message as an INFORMATION MESSAGE.
As it is an information message on ws20000081 application page, system is allowing successful application.
How can I change this information message as an error message u2013any STANDARD settings apart from taking the access key and change it (similar behavior as application as PA30)?
Regards
Thomas
Edited by: Thomas Padiyara on Jun 2, 2011 11:23 AM

Thomas,
The validation can be even done prior to the workflow called. You may have to implement the BADI BADI - PT_GEN_REQ and inside the using the class - method IF_EX_PT_GEN_REQ~CHECK_IF_ACTOR_ABSENT can be used for the validation of this 3 days and generate an error message to portal.
Hope this helps...
Cheers,
Thomas.

Error in standard workflow 200000075

Hi Experts,
I know many people had a problem with the customizing of the standard workflow 200000075. I read all the posts, triple-checked the customizing and it is still not working
When I start my workflow (independent if I start it by creating a PO or by testing it manually) the status is set to "error" (can not see more information about this error).
Message no. WZ703
In the workflow log with technical details I can see following information:
          workflow created
          workflow started
error   exception occured
error   process_node
error   create
error   create wim_handle
error   create via WFM
error   evaluate_agent_via_rule
error   AC20000027
         Error Message Created for Admin
error executing flow work item
error executing flow work item
If I check the WF in transaction SWUD the Event raises the WF, it starts correct.
In transaction SWETYPV I created an entry for the BO BUS2012 realesestepcreated with my workflow and active linkage.
The WF Diagnosis (SWUD) tells me following:
WD:287 Task 'TS20000168' has no agent assignment.
Can anybody give me some help with this?
Thanks a lot,
Christoph

Dear Christoph,
As i understand that the Agent determination standard Rule which you are using 20000027 is not working.
Behind this is a Function module ME_REL_GET_RESPONSIBLE which is being called.
For this you need to maintain entries in the tables T16FW and T16FC.
First you maintain the table <b>T16FC</b> in which you will maintain the
Release Group, Release Code,
Workflow Role - Here Space = No Role Resolution.
                                '1'       = Role Relevant for Workflow
                                '9'       = Role Resolution uses a User exit
                                             EXIT_SAPLEBNF_001 for getting the Users.
I quote from the documentation available through custzomisng here
<i>The Workflow indicator is also used to control role resolution:
"1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
"9 - Role Resolution via User Exit"
Here you use the customer exit M06E0005 to define a role resolution of your own</i>.
You need to maintain these through customising mode and the path is as follows :-
SPRO-> Materials Management-> Purchasing-> Purcahse Order-> Release Procedure for Purchase Orders-> Define Release Procedure for Purchase Orders.
You will also need to maintain the table T16FC through the customising process the same way as given above.
This should definitely solve your issue.
and in T16FW the entries need to have entries like
Release Group, Relese Code, Description,
OT = Here you need to give 'US' for user type
        'O' or organization
        'P' for Person
        'S' for a Position
        'C' for a Job
Agent ID = the agent id created through the Organizational object .
for e.g you can have
release group = X1
release code =C1
Description = 'Release one'
OT = 'US'
Agent ID = 'CHRISTOPH' - SAP User Id of a particular person
Hope this solves yyour issue
Thanks & Regards
Venugopal

Standard Workflow(Approve Document Change) in Error.

Hi Experts,
I have activated a standard workflow from IMG. It is a workflow for approval of Document change (WS21000093). I have assigned the agent as being the workflow initiator. After workflow is triggered, I've executed the work item (approve doc ) from my SAP inbox and it always goes into an error (Read last error).
Can anyone suggest the cause of this error or how to debug this?
Thanks a lot in advance.
Regards,
TM

In the Workflow the Activity stepwhich is having the task TS2100021 in that Task method the below FM is not retruring SY-SUBRC as ZERO that's y it is going into that step check with the data that you are passing to the BOR method
FKK_DOCUMENT_CHANGE_FROM_ID

SAP Standard Workflow for REFUNDS in FS-CD

Hi
We have a requirement to implement SAP Workflow in Financial Services Collections & Disbursements (FS-CD) module for REFUNDS Approval.
Is there any SAP standard Workflow available to meet the requirement?
How to find the Standard SAP workflows available for different Modules (MM, SD, PM, FI, FS-CD etc)?
Correct answers will be rewarded with points.
Thanks
Nikhil.B

Just to add:
The error that I am encountering in the second run/cycle for the PR approval workflow is Import container contains errors (are any obligatory elements missing?)
Basically, WS20000077 will be executed if an approval level is seen. Once the approval is made, then the workflow is also completed. However, for multiple approvers, I only get to execute successfully the first level approval. The succeeding levels are encountering errors as stated above

SAP Standard Workflow for PR Release (with user exit)

Hi SAP WF Gurus,
Good day!
I just wanted to check with you if you have ever used a user exit in the activation of the standard workflow for PR (overall ( release. What we have is a two0step approval process wherein each level has a proxy/alternate approver. We used the available user exit to accommodate this customer requirement since the standard release would only allow us to define 1 approver as a prerequisite for the next level. We were able to execute this on the first level approval; however, we observed that the workflow is not anymore triggered (i.e. does not send work items to agents) for the level 2 release. My questions therefore are:
1. How to set up SWEC? I already executed SWELS and SWEL to check if the events are being created and event linkage is automatically deactivated after running into an error regarding the binding...My initial SWEC setup is for BANF BUS2105 RELEASED On Change. I am assuming that since the workflow was released from the first level, this should be the starting point
2. How to rectify the binding error? I already executed automatic binding in the WF header for the start events but still face it
Your inputs/comments are most welcome
Regards,
DeLo

Just to add:
The error that I am encountering in the second run/cycle for the PR approval workflow is Import container contains errors (are any obligatory elements missing?)
Basically, WS20000077 will be executed if an approval level is seen. Once the approval is made, then the workflow is also completed. However, for multiple approvers, I only get to execute successfully the first level approval. The succeeding levels are encountering errors as stated above

How to activate the standard workflow :ws10000051

hello,experts
    here is my problem:
    I want to activate the standard workflow for document parking :ws10000051 .
     I have already activate the event type linkage in SWE2.
    And then , i maintian obwa , obwj , obwb, obwc, obwd.obwe,obwf.
     In obwa,i choose posting release , subworkflow is ws10000055.
    In obwe, Swf amnt rel is ws10000052.
    In obwf , the org object is the position cfo (myself), before i assign this ,i create a position in ppoce.
   But, when i use f-65 to park a document , i can't receive any workflow in sbwp. I also find "the status of Document Parking (Frame), Parallel is error " in my outbox.
   Can anyone tell me the reason ?
   Thanks !

hi ,hari,
    you are right . when i check swel ,i found ws10000051 : evnet put in the queue . more detail message said :The OPEN_DI of BTE 00002214 could not determine any function modules.
when i check the workflow log (view with technical details), the activity :' determine subworkflow for amount release of document etermine subworkflow for amount release of docu ' status error . the message said :error in workflow customizing for document parkig (transaction obwe).
i don't understand this , because i have already maintian obwe. i made a new entry,like this:
wrkf :1000   (workflow name)
apth: 1000   (workflow approval path)
ammont to : 9999999
crcy: eur
wsf amnt rel :ws10000052
so ,could you tell me more details about this problem ,
thanks

Error in Leave Approval Workflow

Hello Experts,
I'm Using Standard Workflow WS0040077 for Leave Approval . I Activated the Event Linkage in SWEL .Did General Task in Agent Assignment . But when i run transaction PA30 . i get this error in SAP Inbox.
Following error occurred:
00 341
RFC_NO_AUTHORITY
Message text:
Runtime error RFC_NO_AUTHORITY has occurred
SAP System: EDV
Client: 100
Event container appended as attachment.
Event linkage not changed.
Event stored temporarily.
Events can be redelivered via event queue
administration (transaction SWEQADM).
so what should i do to solve this problem.

Hi,
Have you checked the workflow config in SWU3? It sounds like there may be a problem with the LOCAL RFC destination used by workflow. Click the 'Start Verification Workflow' button in SWU3 as a health check.
Also, are you testing this in the right client?
cheers
Paul Bakker

How to use standard workflows in my company?

Hi Experts,
I want to know how do i use standard workflows for my company. I have searched forum, but coudn't find proper answer. I have seen some standard workflow numbers(eg.WS12300111). But when i search for them it wont works. It will pop up "Choose Workflow Template" window. When i select the module there it opens up the empty folders.
What is the meaning of this?
Can i know what do i need to do for overcome this problem?
Thanks,
Rashika.

Hello rashika ,
To differentiate between standard and custom workflows .
All custom workflows would have first three digits lying betwee 900-999 ( called prefix number range )
The number range 90000000 - 99999999 is reserved for customer developmen t and the range 00000000 - 89999999 is reserved for SAP.
Or to know precisely what exactly is the number range of custom workflows in your system , check through tcode OOW4.
To help with your search in HR workflow , I am providing some -
HR -OM
WS01000014     Execute Designated Personnel Action
WS01000038     Consolidate Headcount Planning
WS01000039     Generate Headcount Planning
WS01000040     Create Vacancy for Position
WS01000041     Delimit Vacancy for Position
WS01000043     Error in processing a vacancy
WS01000077     Execute Designated Personnel Action
WS01200136     Message New Employee in Department
HR-PA
WS00400077      Absence approval (asynchr. unlock)
WS00400078     Handling of unapproved absence
WS00400095      Display approved absence
WS00400220      Preparations for start of work
WS00400221      Choose letter
WS00400222      Approve absence (sychr.unlock)
WS01000015      ESS Plausibility check change of address
WS01000036      ESS activities after hiring
WS01200175      Entry due to country reassignment
WS20000003      Pay increase approval with SAP forms
WS20000015      Approve absence
WS20000017      Determine basic pay items
WS20000018      Resubmit postponed pay increase
WS20000057      Find and Lock Employee
HR-TM
WS01000109     Cancel leave request
WS01200003     Find and Lock Employee
WS04200009     ESS Leave Request
WS12300111     General Workflow for Documents
WS12400004     ESS Leave Request Without Approval
WS12400005     Cancel absence
WS12400007     Cancel Absence Without Approval Step
WS20000081     Leave Request with HTML
HR-PY
WS01000090      W-2 form reprint
HR-BN
WS01000001     Initial enrollment Benefits
WS01000002     Create offer and inform employee
WS01000003     Create adj. reason because of event
WS01000009     Check if the employee is locked
Thanks,
sahiba

Error after changes in workflow file (.wft)

Hello Friends,
I have got one customization request in workflow notifications and that required changes in standard packages.
I have made custom copies of those with required changes and then opened workflow file in wordpad and replaced the standard package with the custom copy( I guess this is the method to do it , if there is any other pls let me know) in wft file.
But i am getting errors which indicate that workflow is not able to call the custom components. The error is saying that package is invalid but when i checked from backend , the package status is valid.
Is this an issue with access level in workflow?
Please help.
Regards,
Amit

Oracle Application Version : 11.5.10.2
Database Version : 11g Enterprise Edition Release 11.1.0.7.0
Event Error Name: WFE_DISPATCH_GEN_ERR
Event Error Message: 3835: Error '-20002 - ORA-20002: 2018: Unable to generate the notification XML. Caused by: 2020: Error when getting notification content. Caused by: ORA-04061: existing state of has been invalidated
ORA-04061: existing state of package "APPS.EPO_WF_REQ_NOTIFICATION" has been invalidated
ORA-04065: not executed, altered or dropped package "APPS.EPO_WF_REQ_NOTIFICATION"
ORA-06508: PL/SQL: could not find program unit being called: "APPS.EPO_WF_REQ_NOTIFICATION"
wf_notification.GetAttrDoc2(1049594, PO_REQ_APPROVED_MSG, text/html' encountered during execution of Generate function 'WF_XML.Generate' for event 'oracle.apps.wf.notification.send'.
Event Error Stack:
WF_MAIL.GetLOBMessage3(1049594, WTCRD172, 2020: Error when getting notification content. Caused by: ORA-04061: existing state of has been invalidated
ORA-04061: existing state of package "APPS.EPO_WF_REQ_NOTIFICATION" has been invalidated
ORA-04065: not executed, altered or dropped package "APPS.EPO_WF_REQ_NOTIFICATION"
ORA-06508: PL/SQL: could not find program unit being called: "APPS.EPO_WF_REQ_NOTIFICATION"
wf_notification.GetAttrDoc2(1049594, PO_REQ_APPROVED_MSG, text/html)
Wf_Notification.GetAttrDoc(1049594, PO_REQ_APPROVED_MSG, text/html)
Wf_Notification.GetText(1049594, text/html)
Wf_Notification.GetBody(1049594, text/html)
WF_NOTIFICATION.GetFullBody(nid => 1049594, disptype => text/html)
WF_MAIL.GetLOBMessage3(nid => 1049594, r_ntf_pref => MAILHTML), Step -> Getting text/html body)
WF_XML.GenerateDoc(oracle.apps.wf.notification.send, 1049594)
WF_XML.Generate(oracle.apps.wf.notification.send, 1049594)
WF_XML.Generate(oracle.apps.wf.notification.send, 1049594)
Wf_Event.setMessage(oracle.apps.wf.notification.send, 1049594, WF_XML.Generate)
Wf_Event.dispatch_internal()

Move In Standard Workflow (ISUACBMOVEIN) : Automatic Owner Allocation Proc.

Hello Experts,
In the automatic owner allocation process, when we move out the tenant the owner is supposed to automatically move in with the pre-configured offset. In my case the workflow was not being triggerred so we defined the the linkage of the events (tcode: SWETYPV). After doing this we got an exception
"Object MOVEINDOC method MOVEINOFOWNERCREATENODIALOG cannot be executed" with error EQ067 (Check the reference for move-in document &1).
When I see the standard workflow I see that it analyses Contract Account and verifies what category it belongs to Residential or not and splits it into two paths one for Residential and one for non residential. Then it passes through "template Movein Doc for". Here it provides a Move in Doc Reference as 000000004712 for non residential and 000000004711 for residential customers in a container operation.
This is where the problem is. These donot exist in Move in / move out tables. So how do I approach now
1) Is there any standard reference document already present in SAP system which can be configured?
2) Do I have to copy the standard workflow and edit the template to give different reference document numbers?
Or is there any other way to solve this issue?
I really appreciate all the help i am getting from this forum so far.
Thanks a lot.
Vinay.

Hi Vinjay,
we are using different method to create a owner move-in MOVEINDOC->MDTMOVEINOWNER which doesn't required the reference.
However, for your answer, you should check out these SAP help:
http://help.sap.com/saphelp_rc10/helpdata/en/43/a7b39d823017b5e10000000a1553f6/content.htm
http://help.sap.com/saphelp_rc10/helpdata/en/43/a24f89794e274ee10000000a422035/content.htm
Regards,
Chaiphon

Error in the Transfer Workflow

Hi,
I am using the standard workflow for the Internal Transfer (WS50000031). I have activated the workflow, its working fine other than a single error. Like when the manager transfer a person, its going to the next level(first level) manager. but he cant able to see the form. But the second level manager ( superior for the First level manager ) is receiving the form with the details like who has got transfered, etc.
How can i resolve this issue. Whether the Workflow itself delivered like this.
Please help me to solve this issue.
Thanks
Ram.

Ram,
Could you give us a little bit more information on this. You have mentioned that the first level approer cannot see the form. Does that mean that he is getting the workitem but he cannot see the form (may be as an attachment or something)?
I checked the Standard SubWorkflow that is being called, and a Standard Rule is being used. So the agent determination is done using the same rule for both the first level and the second level.
Regards,
Anwar.

Error in PR standard workflow WS20000077

Similar Messages

Maybe you are looking for