SC workflow - "set status to released" step tRFC error

Hi All,
We have a "Shopping Cart without approval" workflow defined in our SRM system.
The workflow is working fine in Develpoment scenario however in Production it is stuck at "set status to released" step.
Checked that step and its a backgroung step with tRFC Object type.
When we click on tRFC Object Type it opens up "Transactinal RFC" screen with msg "error during tRFC call" and tRFC destination field as WORKFLOW_LOCAL_500.
Any help is this regard will be highly appreciated.
TIA
Regards,
Richa Sinha

Hi RS,
havent worked on SRM WF's,
check with BASIS on the Automatic WF Settings in SWU3 tcode, as you maintain RFC there, may be the RFC node in SWU3 is not active or something.
Hope it helps.
Aditya

Similar Messages

HELP - SWO1 - ERROR WHEN SETTING STATUS FOR RELEASED

Hi my friends,
I need to create a wf to PositionHR aproval.
I've already copyied the PDOTYPE_SH object to Subtype ZPDOTYPESH on SWO1 Tnx.
Now, I'm trying to set the object and methods status for "released". But SAP is giving me the following error message bottom:
- Please set required status for supertype first.
What can it be ?
tanks,
Glauco

Ho Glauco,
Check whether object PDOTYPE_SH is in Released status (it is not released in my 6.20 system). Check if you can set the status of ZPDOTYPESH to Implemented. You should be able to work with the object in Implemented status. I suggest that you post a message on OSS whether SAP recommends using the PDOTYPE_SH object since they have not released it.
Please post any future Workflow related questions in the Business process management (BPM) forum, the new home for Workflow.
Cheers,
Ramki Maley.

SP2010 Designer workflow "Set Content Approval Status" does not work

Hello
I'm having a problem with a workflow for one of my clients.It is a SharePoint 2010 environment and I can only use SharePoint 2010 designer (no visual studio).
We have an approval workflow in place, which works great. After the document approval workflow has does its thing, a new workflow can be launged by specific users (they have writing rights and can approve content). The workflow is used to set the release
date of the document. This can only be determined after content approval.
However, when the release date is set, the document approval status is changed to concept. This is of course to be expected, as we changed to document metadata. That is why I wanted to add the action "Set content approval" to this workflow. I cannot
seem to get this action to work. Right now the workflow does the following:
check out the document (check out is obligatory in our library)
set the release date field to the released date parameter (defined when starting the workflow)
check in the document
set content approval to approved.
The release date gets set to the parameter value, but the document is not checked in and the content approval status is not set. SharePoint produces the following error message (translated from Dutch): "An error occured. Cannot edit the item, possibly
because one or more columns require another type of content. Unknown error."
Guided by other posts online I gathered that this might be because the actions checkin and set content approval occur to close together. I tried letting the workflow pause for the duration of 1 minute after checking in, but this pauses the workflow indefinitely.
I then tried 5 minutes (as this is the time standard set by SP2010 designer) but this also resulted in indefinite pausing.
Posts online lead me to believe that I'm not the only suffering from this problem, but as of yet, I haven't been able to find a solution that works for me. Hopefully someone can help me.

Hi,
According to your post, my understanding is that the "Set Content Approval Status" didn’t work in SharePoint 2010 Designer workflow.
I try to reproduce the issue and the result is the same as yours.
If I only check out and check in the item, the workflow works well.
However, once I set Content Approval Status after checking in the item, the workflow get error.
As a workaround, I recommend to use two workflow to achieve what you want.
First, create the first workflow, and allow the workflow to be manually started.
Then, create the second workflow, and
start the workflow automatically when an item is changed.
When you start the first workflow, the document will be set value of the release date. And then the second workflow will be started automatically to set the content approval status.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

WS20000075: work item of 1st release step stays in status In process

Hi All,
I have activated and set up standard flow WS20000075 but the work item of 1st release (PO release strategy with 3 levels) step stays in status In process. The work item for the 2nd and 3rd release step are completed as expected.
What could cause only the work item of the 1st release step to stay In process?
Thanks a lot in advance

Hi,
I cannot see in what field the release code is filled in EKKO.
See here SWEL after 1st release:
And SWEL after 2nd release:
EKKO after 1st release
EKKO after 2nd release
release strat
Release strategy

How processing status "In Release " is set in purchase requisitions

Hi Experts,
How processing status, iun release is set in item details (Status tab page) of purchase requisition, also is it possible that release status is "release completed" even requisition is not subject to release strategy.
how release active is set.
Thank you
Anand

Hi
The Stauses in the PR will be active opnly if you have the release strategy setup for the PR.
"In release" is set when the PR is created & is subjected to approval & in the approval process.
Relased is set when the PR is approved fianlly.
Thanks & Regards
Kishore

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.

Set the status on Released Trade Promotions to Finished if TP has expired ?

Hello,
I would like to do a development of report that sets the status on Released Trade Promotions to Finished if TP has expired, i.e. passed the End Date of the TPM.
The report should first search for all active trade promotions, i.e. all trade promotions that have the status "Released", i.e I1004 and then compare the end date of Trade Promotion with the date the report is run and if the end date has been passed then the system status should be changed to Finished, i.e. I1008.
Example:
We are running the report on 16.02.2009 and it finds the Trade Promotion below which has System Status I1004. Then it compares the date of running this report which is 16.02.2009 with the end date of Trade Promotion wich is for example 15.02.2009, since the date has been passed, the trade promotion has expired and thus the System Status should be set to I1008 "Finished" so that it can no longer automatically into a Sales Order.
I would like to know how can I do this ? or in which Implementation Name can I do the modification ?
Thanks in advance for your help
Amirovic

Hello All,
I will explain my request better :
Iu2019m looking for help. I'm working in CRM 2007 and I need a template of similar report where I can find this requirement:
I have to create a report to set the status on Released Trade Promotions to Finished if Trade Promotions has expired, i.e. passed the End Date of the TPM.
The report should first search for all active trade promotions, i.e. all trade promotions that have the status "Released", i.e I1004 and then compare the end date of Trade Promotion with the date when the report is run and if the end date has been passed then the system status should be changed to Finished, i.e. I1008.
Example:
We are running the report on 16.02.2009 and it finds all the Trade Promotion which has System Status I1004 u201CReleasedu201D. Then it compares the date of running this report which is 16.02.2009 with the end date of Trade Promotion wich is for example 15.02.2009, since the date has been passed, the trade promotion has expired and thus the System Status should be set to I1008 "Finished" so that it can no longer automatically determined into a Sales Order.
Thanks in advance for your help
Best Regards,
Amir
PS: This report should be running in the background as a daily job.

Rejection of Purchasing Release Step (No Workflow)

Hello gents,
I have set up a release strategy witth 3 leves, no workflow activated. Assume that manager at last level (3) denies the release.What is the best way for the manager of level 2 to be aware of it?
Thank you for any advice...

Hi
Like PO, you can unrelease it in ME35K if it is not transmitted to vendor. If it is transmitted to vendor, then you need to delete the line item in contract if PO is not created against it. If PO is created then you need to modify the quantity in which equals the PO quantity so that new POs will not be generated. This is as same as amendment. If you have version management active for your document type it would be helpfull in printing amended contract and transmit to vendor that contract is rejected or cancelled
Regards
Antony

Workflow for MM purchase Requisition steps required

Dear all,
        I am trying to configure purchase requisition Workflow.
        I am working with Work flow, WS 00000038
        I have assigned agents to TS 20000162
        Now how to proceed further, do i need to maintain some more settings
        or i should try to test system.
        Regards,
        Gaurav sood

Under the assumption that things have not changed much since 4.70, here's quick introduction:
The workflow is started only when a relevant release strategy is found, so customizing of release strategies is a very important (first) step here.
In the Implementation Guide you find the customizing in the following path:
Materials Management
-- Purchasing
-- -- Purchase Requisition
-- -- -- Release Procedure
-- -- -- -- Procedure with Classification
Only the procedures with classification are relevant if you want to use workflow to notify about requisitions waiting for release.
First you must set up a classification class if that has not already been done. Derive your characteristics from the structure CEBAN. The online help is not too bad, I had never set up classifications before and managed to get it working.
If you need data that are not available in CEBAN, or you want to modify them for the purpose of determining the release strategy there is an enhancement you can implement, and there are customer fields you can use. The enhancement definition's name is M06B0002.
As an example of what you can do, I have used it to set the company code in one of the customer fields, and to change the account assignment type. However, whether you need this enhancement or not depends strongly on what data you use to determine your release procedures (a step in customizing you will get to later).
When that is done you define release groups and release codes. Release codes are defined within each release group. Whether you should use one group or several groups is often a matter of choice.
I myself prefer using several groups even if I don't have to, so long as it doesn't lead to having to define duplicate release strategies (which you will soon get to). So, if there is some characteristic that clearly separates your release strategies, e.g. the highest amount that does NOT require release etc, you can define one group for each value (group) of this characteristic.
For instance, if some company codes require release for everything worth more than 100EUR while the default is to require release from 10.000EUR you could create to release groups. None of your release strategies will be duplicates since the value from which release is required will be different and you thus need to have that as a characteristic.
You then check that the set-up of release indicators is OK, and then you are ready to start defining the strategies. Release stragies are defined within each release group, and use one or more release codes (two or more release indicators).
It is fairly self-explanatory once you get into the screens. The thing to be observant about is to not define overlapping strategies, as this will prevent the solution from working.
When you are done, and have tested the solution in DEV it is time to transport it to the QA system. That's when I got a rather unpleasant surprise. The classification data are not transported, so both the characteristics and class, as well as the classification data in each release strategy had to be redefined. And in roughly two hours I have to do it again in production.
It is possible to transport classification information, it is described in SAP OSS Notes (different solutions for different versions).

Creating workflow for purchase order release.

Hi friends
I want step by step detail about creation of workflow for purchase order release..
After release purchase order it will goes to the two level of approval..
after that the workflow should be completed...
how can i develope the workflow for that scenario..
Thanks
Gowrishankar

Hi Gowrishankar,
You can get step by step workflow for PO using standard workflow
<b>Release of Purchase Order :WS20000075</b>
And for two levels of approvals you have to configure in SPRO the path is
Purchase Order:
SPRO> Material Management->Purchasing->/Purchase order-->Release procedure ---> Procedure with classification ---> set up procedure with classification ---> double click on Release strategies and Workflow.
If you don't know about this configuration, you have to confirm with your MM consultant.
Thanks and Regards,
Prabhakar Dharmala

Workflow for P.O release process.

Hi Guys,
As per the one of the thread I have done setting as per the below. Ref last 10 line for the details of the problem.
Hi,
1) Work flow: - Work flow is standard functionality of SAP.
I give one example to u.
In the case of purchase order creation, First purchase person create purchase order, then first purchase order approved by purchase head and then auditor approved purchase order on print of purchase order.
With work flow you can send soft copy of purchase order to both person purchase head and auditor to approve your purchase order.
Due to this your process for purchase material is faster then manual process.
2) You can implement work flow in purchase order release strategy with below mention detail.
For mail facility, you need to activate workflow for PO release procedure;
*Go to SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders *
Define Release Procedure for Purchase Orders > Release Codes >
here assign Workflow indicator as "1" against each Release Code
Now come to SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders >
Define Release Procedure for Purchase Orders > Workflow >
Here against each release code assign OT as US and respective User ID's for Release Codes.
Now Go to OOCU > here under MM, go to MM-PUR,
Now click on "activate event linking"
Here open "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button
Here activate "Event linkage activated" and also activate "Enable usage of event queue" and Save data.
Same way and click on "Assign agents" and proceed all above steps.
Now create a PO and check the SBWP for SAP Mail of respective Users
This was the details given by the thread but now I have completed till
OOCU > here under MM, go to MM-PUR,
Now click on "activate event linking"
Here open "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button
Here activate "Event linkage activated" and also activate "Enable usage of event queue" and Save data.
For proceeding futher as said in the above procedure. I am getting User ID inside WS20000075 when I click on Assign Agents but I am not getting the details button to repeate the step as said.
Please let me know whatever I have done is enough to get the mail or is there any thing else need to be done.
Thanks
Dhanu

Hi,
release code and release group should be assigned in the authorization object for the approving authorities.
apart from this the settings looks ok and it will work

Additional PR release step in current release strategy

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 first 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 how to implement the additional release step. Thanks.

Hi Arghadip,
Thanks for your reply. My intention to create different doc type is for separate set of release strategy.
In current release strategy, for example, if doc type = NB, creation indicator = manual and the total value of PR is $1K, then the PR requires release code A1 for approval and the approval is align with the company finance policy. The manager (with release authority A1) of the PR creator then selected by the user exit and assigned with workflow task.
For the request for additional release step, if doc type = ZS, creation indicator = manual and the total value of PR is $1K, then the PR requires release codes AA and A1 (new release strategy). The user exit will assign a dedicated position/user (not necessary the manager of the PR creator) for release code AA, and then assign the manager of the PR creator for release code A1. Therefore, even the total value of PR is also $1K, but since the PR item contains material group 80501, then the PR require an additional approval on top of the $1K financial approval.
Your comment is welcome. Thanks again.

Prevent Material PO creation till WBS status is released

Hi All,
Please suggest how can I prevent creation of material PO giving WBS assignment till WBS is released.
I know I can control it through System Status (Drawback is cross client setting) and User status.
Anyother method?
Thank You
Regards
Maneesh

Hi,
This is standard functionality in SAP that you can create PR and PO without allocating budget to the WBS Element.So create a user status that will prohibit the system to create PR and PO in CRTD system status.
The steps are:
Go to OK02 and create a user status .
then create two statuses NBUD and BUDG.
1.under NBUD & BUDG choose object type WBS .
2.In NBUD Forbid the Material purchase order,Material Purchase Requistion and Release.
3.In BUDG set Budgting and allow Release.
So system will not allow to release a project without allocating Budget.
Once you allocate budget system will change the status from NBUD To BUDG.
Take care.
Muzamil

Workflow Internal Status: Cancelled

Dear All,
We have a SharePoint/Project Server 2013 Enterprise Edition and Sharepoint Designer deployment in HYPER V virtual environment. We are using it for Project Management. We are facing an issue while designing a workflows in SharePoint
designer 2013.
PROBLEM DESCRIPTION:
“Workflow Internal Status: Cancelled
" ERROR:
RequestorId: 7b51f972-22ad-faa7-a60a-20f365bff1e3. Details: System.ApplicationException: HTTP 500 {"SPRequestGuid":["7b51f972-22ad-faa7-a60a-20f365bff1e3"],"request-id":["7b51f972-22ad-faa7-a60a-20f365bff1e3"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["116"],"SPIisLatency":["0"],"MicrosoftSharePointTeamServices":["15.0.0.4481"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Date":["Tue, 24 Dec 2013 19:28:11 GMT"],"Server":["Microsoft-IIS\/7.5"],"X-Powered-By":["ASP.NET"]} at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext
context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager
bookmarkManager, Location resultLocation) "
Workflow stage status: Workflow is still in processing please refresh the page and try again
After configuring the workflow in SharePoint designer followed below mentioned TechNet blog to go through the workflow designing
URL: http://msdn.microsoft.com/en-us/library/office/jj163494.aspx
As in the blog project Event is set to when project is submitted, we tried a lot to submit the project but submit button was grayed out and unable to do this, then we changed to event
when project is committed from that above mentioned errors are occurred. Moreover we have tried to make simpler workflow but same result.
Detailed Description:
Installation of Workflow Manager 1.0
Installation of Service Bus and CU1
Start App Management Service (Also Configured in Managed Service App)
Start User Profile Service (Also Configured in Managed Service App)
Run the full user profile sync and Completed
Created the workflow using domain user account and assigned him proper permission
Thanks in Advance
REGARDS DANISH DANIE

If the workflow initiator does not have write access to the hidden Workflow History List, the same error happens.
To solve the issue, simply open the hidden list permission (through SharePoint Designer>All Files>Lists, for example) and make sure to have your potential initiators contribute rights. The list defaultly inherits the site's permissions.
kirtesh

Error in Workflow for PR Overall Release

Dear SAP Fans,
I am getting error in workflow (WS20000077) after release of Purchase Requisition with first person and getting message in OutBox with the following errors and is unable to go to next person's Inbox for release PR.
   Error when creating a work item
   Error when processing node '0000000004' (ParForEach index 000000)
   Error when creating a component of type 'Etapa'
   Error when starting work item 000000392108
   Agent determination for step '0000000004' failed
   Error in resolution of rule 'AC20000026' for step '0000000004'
   No configuration for workflow WS20000077 version 0001
   Work item 000000392108: Object FLOWITEM method EXECUTE cannot be executed
How can I correct the above errors. Please help me !!!.
Thanks in advance,

HI,
Just a thought,
Please check, If some one changed WF-USER password.
also check if the WF-USER is a Service user and not dialog user.
Regards,
-Venkat.

SC workflow - "set status to released" step tRFC error

Similar Messages

Maybe you are looking for