PO Workflow release

Hi guys,
i created release strategy. I have problem with PO WF configuration.
In SPRO I assigned my SAP login to the release strategy. The problem is that when I create PO I do not receive new message in SBWP. As far as I know WF has been activated.
Help me pls to solve this problem.
reg.
Piotr

Hi,
To receive the message triggered on each release the Task 200000168 has to be assigned with your user ID in the agent assignment of the Task .Or if OM is propely defined than it should get the user id to whom the Task <u>Release of purchase order effected</u> should go.
Dhruba

Similar Messages

How to approve or release a Custom workflow release strategy using a prog.

Hi There,
I am working with a custom transaction with release strategy using custom workflow. I am done with the module pool and workflow templates. And also I can able to start workflow using the FM SAP_WAPI_CREATE_EVENT.
My actual Issue is I have set of buttons in the module pool screen with names Approve (1 to 5) and Reject (1 to 5). When I press the "Approve 1" release strategy of the first person need to approved. Is there any Function Module or Classes for approving the workflow release strategy using buttons in screen.
Thanks in advance,
Viruman

Hi
Make use of the function module SAP_WAPI_DECISION_COMPLETE. To this function moduel pass the workitem ID and pass decision parameter value as 0001 for approve and 0002 for rejection action. You can check in this forum with this function module you will find lot of threads.
If its not a decision step then you can make use of SAP_WAPI_EXECUTE_WORKITEM or SAP_WAPI_WORKITEM_COMPLETE.
Regards
Pavan
Edited by: Pavan Bhamidipati on May 26, 2011 11:43 AM

Workflow release for payment two stage

Hello Friends,
I have found one workflow as WS00400021 which suits my requirement and i have read plenty of doucmentation on the same but im not getting the actual step that is from where i have to start to activate this workflow.
Can any one pls guide me tht from where to start first ie first we have to define agent or postions or event linkages , assignment of task etc and all.
Helpful answers will be rewarded.
SUnny

Hi Suny,
You have to define your PO release strategy in the SPRO first.
Materials Management->Purchasing->Purchase Order->Release Procedure for PO

Workflow Release Strategy

Hello Experts;
I have a requirement for PO release strategy for a dept of 20 PM's and each PM have to release his own PO, currently the buyer drills down to the order or Network (PO account assignment) to see the person resp then send him the PO # for approval.
I was thinking creating a doc type for each PM then have the buyer select the doc type based on the info on the account assignment to find the approver then do my config for object type and agent ID's.
Any suggestion would be appreciated.
Thanks;
Ibou

Hi,
You can try this approach -
Store the relevent doc types names and buyers in a z table and pick up the recievers in the workflow from that table using conditions for that particular step.
See if it helps you
Regards,
Ribhu

Po workflow( release strategy)

hi,
we had defined release strategy for po workflow. i assigned the users to release codes in SPRO. what my doubt is .... is there any further configuration is there to go purchase order to agent inbox.
i am not defining workflow template.
is it required define workflow template for po, or is it sufficent release strategy.
let me give reply asap,
thanks
suresh

Hi,
You MUST have the workflow template for PO release strategies.
There is a SAP standard workflow, which you need to activate for the workitems to go to respective agents.
Hope it helps.
Regards,
Shashank

Workflow release PR

Hi everyone,
I'm trying to set up the workflow for the release of a PR. I copied the standard-WF (WS20000077), activated the link in OOCU, and filled out the release strategies in SPRO.
When I create a PR, the event is not triggered...
It's the first time I start from scratch, so I must be doing something wrong, but what ?
thanks for the assistance !

Hi Bjorn,
the events are only triggered when using the release procedure
"with classification".
Are you using this one?
There will only be workflow events triggered, if the purchase requisition is subject to release. In order to verify this, press the check-button when creating a purchase requisition. A new header tab with name "Release strategy" has to appear. If not, you have a problem with the classification or... (please see next paragraph)
Furthermore please check the customizing of the document type (e.g. NB): You'll need the check box "Overall release" set there.
Basically that's it for the very first steps.
Please let me/us know, if it helped.
Best regards,
Florin
Cross-posted to SAP-WUG
P.S.: Björn is talking about PR (requisitions), so the transactions used are ME5xN
P.P.S.: If an event is not traced at the (fully activated) event log, it never can be a misused binding.

Workflow - Release of Vendor changes

Hi,
I have defined a workflow that one user creates the changes on a vendor and another releases them. When the release is done the data which is saved in a Z-table should be transferred via UPDATE into the standard vendor table.
1. How can I realize this function?
2. How can I debug the release?
Thanks a lot for your help.
Robert

Hi Rose,
thanks for this answer. I know that I need a method to call this function but where do I have to place the call. Do I have to place it in the relevant task or is there a place where I can set the call within the workflow?
Thanks again for your help.
Kind regards
Robert
P.S.: Maybe the questions are really simple but I have not really experience with workflow and tasks.

Workflow Release steps

Hi,
We have 4 approval levels for PO. Once I create the PO and save, a mail is sent to the 1st approver(requisitioner). After the first level approver approves then it should go to the next approver and same for other approver levels.
my problem is once the first approval is done then all the other 3 approvals are done in background immediately without waiting for other approvers. I tried checking but unable to find the rootcause of the problem. can some help to fix this problem. Thanks.
Regards
MS

Hi MS,
I am not very sure if I understand the issue completely, but I guess you are facing the issue that after the 1st approval all the next 3 levels of approvers get the workitem for approval at the same time.
If yes, then please check the workflow template design as to how the approval flow is made. The approval flow should be designed sequentially so that the workitem goes from one approver to another after the preceeding approval is done.
Regards,
Saumya

Purchase order release workflow - urgent

Hi friends
When iam creating purchase order it trigger the workflow WS20000075 for releasing purchase order in that purpose what can i do..
How can i set the Agents
How can i trigger the events - i think in that purpose using pftc we trigger the workflow.. so i need clear steps from beginning onwards..
my exact requirement
once i create purchase order, the workflow will be triggered..
after that the mail goes to the approver.. if he/she click that mail purchase order release statement want to be open.. after that he/she release purchase order it will goes to the next level..anyone give the step by step procedure..for that
Thanks
Gowrishankar

yes prabakar.. but iam confused..
You can get step by step workflow for PO using standard workflow
Release of Purchase Order :WS20000075
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.
after finish this iam triggering events using pftc
in that pftc iam choosing business object bus 2012 for po release..
i think thats enuf..
After that it is possible to trigger workflow.. when iam create purchase order..
Thanks
Gowrishankar

Workflow Flow Release Approval

Dear All,
I have Workflow Issue and i am sending my Requirement Go Through it .
Issue:
I am using F-67 forcustomer credit memo parking my requirement is if I post below 500/- SAR thedocument should not lock and the accountant can release the document throughFBV0 t-code and if the accountant post above 500/-SAR than the document should lock and accountant cant able to release above 500/-SAR document Through FBV0 T-code only it must be released by the Finance Director.This I want to configure in Workflow, Release Approval Level in T-code SWDD.
Get me out of this as i am very new to workflow as i am FICO Consultant.Your earliest reply on above is requested.
Regards,

Hello,
after checking linkage and Workflow .
i'm getting this error.
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.

WS20000263 Workflow configuration in Treasury (Business partner approval)

Hi Experts,
Currently we are doing an SAP Upgrade from 46C to ECC 6.0 (Enh. 4) and in Treasury we cannot solve a problem. There is a workflow (id: WS20000263) which is used in case when the BP is created or changed. This workflow was used in 46C, but in ECC 6.0 this is changed (in the new system the BP is managed in a different way as it was in 46C - Central Business Partner).
The problem is that the workflow is not working: I am not even able to do the proper configuration. There are some contradictory parts in SAP help which confuse me! (i.e.: in SPRO in "Active Release" config point, it says "activate the release object CBP SAP Business Partner". But the table - which contains this configuration point - is filltered for "ZBP" object, which means i can activate only the "ZBP" object and never the "CBP" object. The other point is that I cannot add "CBP" value in a "proper" way...)
I hope any of you faced with this workflow configuration and help me out or at least give me some advices.
Thanks in advance for your help!
Best Regards,
Attila

Hello Atrtila ,
Good Morning.
can you please tell me how your problem is solved.i am facing exactly the same issue in our system.exactly same thing.workflow release is getting triggered on changing any business partner role but not triggering at the time of creating a new line in business partner role .
please help.
Vijay Agarwal.

Workflow in starting or stopping status

Hi All
iam in ebs r12 12.1.3 db 11gr2 11.2.0.3
when stop or start workflow notification. i have status STARTING OR STOPPING.
I did shutdown application , bounced database ran cmclean.sql
restart the database and application and still have the same error in the status.
Please advice what else i can check.
Thanks in advance.
COMPONENT_NAME COM_STAT
ECX Inbound Agent Listener STARTING
ECX Transaction Agent Listener STARTING
Workflow Deferred Agent Listener STARTING
Workflow Deferred Notification Agent Listener STARTING
Workflow Error Agent Listener STARTING
Workflow Inbound Notifications Agent Listener STARTING
Workflow Notification Mailer STOPPING
WF_JMS_IN Listener(M4U) STARTING
Web Services OUT Agent STARTING
Web Services IN Agent STARTING
Workflow Java Deferred Agent Listener STARTING
COMPONENT_NAME COM_STAT
Workflow Java Error Agent Listener STARTING
Workflow Inbound JMS Agent Listener STARTING
Using these notes and test the SMTP the mail was sent fine.
Workflow Notification Mailer Remains in Starting Status [ID 1400353.1]
How to Perform a Meaningful SMTP Telnet Test to Troubleshoot Java Mailer For Sending Email Notifications [ID 753845.1]
here is a portion of the log.
[May 19, 2012 12:39:50 AM PDT]:1337413190218:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:1627058645:69856:1337410068910:2:PROCEDURE:[fnd.wf.apps.WorkflowContext]:oracle.apps.fnd.wf.apps.WorkflowContext.getJDBCConnection: END: returning oracle.jdbc.driver.T4CConnection@1700391
[May 19, 2012 12:40:50 AM PDT]:1337413250224:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:1627058645:69856:1337410068910:2:PROCEDURE:[fnd.wf.apps.WorkflowContext]:oracle.apps.fnd.wf.apps.WorkflowContext.getJDBCConnection(): BEGIN/END
[May 19, 2012 12:40:50 AM PDT]:1337413250224:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:1627058645:69856:1337410068910:2:PROCEDURE:[fnd.wf.apps.WorkflowContext]:oracle.apps.fnd.wf.apps.WorkflowContext.getJDBCConnection(null,0x119e583,false,false,false): : BEGIN
[May 19, 2012 12:40:50 AM PDT]:1337413250224:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:1627058645:69856:1337410068910:2:PROCEDURE:[fnd.wf.apps.WorkflowContext]:oracle.apps.fnd.wf.apps.WorkflowContext.getJDBCConnection: END: returning oracle.jdbc.driver.T4CConnection@1700391
[May 19, 2012 12:41:50 AM PDT]:1337413310231:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:1627058645:69856:1337410068910:2:PROCEDURE:[fnd.wf.apps.WorkflowContext]:oracle.apps.fnd.wf.apps.WorkflowContext.getJDBCConnection(): BEGIN/END
[May 19, 2012 12:41:50 AM PDT]:1337413310231:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:1627058645:69856:1337410068910:2:PROCEDURE:[fnd.wf.apps.WorkflowContext]:oracle.apps.fnd.wf.apps.WorkflowContext.getJDBCConnection(null,0x119e583,false,false,false): : BEGIN
[May 19, 2012 12:41:50 AM PDT]:1337413310231:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:1627058645:69856:1337410068910:2:PROCEDURE:[fnd.wf.apps.WorkflowContext]:oracle.apps.fnd.wf.apps.WorkflowContext.getJDBCConnection: END: returning oracle.jdbc.driver.T4CConnection@1700391
[May 19, 2012 12:42:36 AM PDT]:1337413356004:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:-1:-1:ANONYMOUS(-1):-1:Thread[Cache Stats Writer,5,main]:1627058645:69856:1337410355410:4:PROCEDURE:[fnd.common.WebAppsContext]:oracle.apps.fnd.common.WebAppsContext.getJDBCConnection(): BEGIN/END
[May 19, 2012 12:42:36 AM PDT]:1337413356004:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:-1:-1:ANONYMOUS(-1):-1:Thread[Cache Stats Writer,5,main]:1627058645:69856:1337410355410:4:PROCEDURE:[fnd.common.WebAppsContext]:oracle.apps.fnd.common.WebAppsContext.getJDBCConnection(null,0x25491d,false,false,false): : BEGIN
[May 19, 2012 12:42:36 AM PDT]:1337413356004:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:-1:-1:ANONYMOUS(-1):-1:Thread[Cache Stats Writer,5,main]:1627058645:69856:1337410355410:4:PROCEDURE:[fnd.common.WebAppsContext]:oracle.apps.fnd.common.WebAppsContext.getPrivateConnectionFinal(null,0x25491d,true,false,false): : BEGIN
[May 19, 2012 12:42:36 AM PDT]:1337413356004:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:-1:-1:ANONYMOUS(-1):-1:Thread[Cache Stats Writer,5,main]:1627058645:69856:1337410355410:4:PROCEDURE:[fnd.common.WebAppsContext]:oracle.apps.fnd.common.WebAppsContext.borrowConnection(null,0x25491d,false): : BEGIN
[May 19, 2012 12:42:36 AM PDT]:1337413356005:-1:-1:abc1-ap1.test.com:10.10.6.200:-1:-1:-1:-1:ANONYMOUS(-1):-1:Thread[Cache Stats
Edited by: user3715462 on May 21, 2012 10:46 AM

it worked before but just had problem today.. i did not change anything.Please set the Workflow Mailer Log Level to Statement and restart the Workflow Mailer and check the log files then.
Unable to Connect to Mail Store in Workflow Notification Mailer Logs [ID 741352.1]
Troubleshooting Workflow Java Notification Mailer - Technical Reference [ID 1191125.1]
Also, please run workflow diagnostic scripts as per (Oracle Workflow Release 12 Diagnostics [ID 469822.1]).
Thanks,
Hussein

All queries in workflow 2.5 running on 10g slow .. recently

Hello,
I would really appreciate any help in this regards. I have a table that has
350,000 records in the database. We recently migrated from 9i to 10g.
select context from wf_notifications
where begin_date > sysdate - 1;
While in 9i, the following query used to run under a second.
While in 10g, the following query ran for 6 minutes.
(# of rows returned = 11)
if we modify the query to THE following, then it takes about 10 seconds.. but
not as efficient as 9i but acceptable.
select /*+ RULE */ [col] from [table]
where [date_col] > sysdate - 1;
PLEASE HELP. WHAT WENT WRONG. Respond to [email protected]
Regards

Hi,
Probably not the answer that you're after, but...
I think that only workflow release 2.6.3 is certified against a 10g database. I don't think that 2.5 is supported against the most recent database releases - if you check certify it will tell you.
Sorry that doesn't answer your problem, but you might find that you need to upgrade to the latest version of WF to match your DB level.
Matt

Payment proposal workflow

Hi friend,
<Moderator note: new question related to [this thread|custom pushbutton created in the transaction F110;. Please always ask new questions in a new thread. See the [Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] for further info>
Did you got your task done already? I got a quite similar request which request to start the workflow when the payment proposal has been list and confirmed, the system needs to send out an email for all vendor in the transaction list. Could you please let me know whether can I use the above Business Object BUS2021 in my task. or please kindly give your good advices, since I am a fresher and no experience.
Thank You Very Much.
Jc
Edited by: Mike Pokraka on Aug 18, 2008 3:06 PM

Hello,
Delegate if you can. Create a custom one only if absolutely necessary.
"how can I make the custom workflow trigger with the event"
Define the event as a starting event of the workflow.
"Why is the standard workflow "Release for payment single step" is not being triggered when a payment proposal is made ?"
Maybe the linkage has been disabled by default.
regards
Rick Bakker
hanabi technology

Pr release process

hi expert
I want to configure pr release stratgy can u tell me what are the setting to be done step by step and our campany have got one plant
Thanks & regards
vijay

HI
Release Procedure - Procedure in which one or more authorized persons (e.g. a cost center manager) give(s) the go-ahead or "green light" to procure a material or external service.
(Release Procedure for PR, RFQ, PO, Contracts & Scheduling Agreements)
The following purchasing objects can be released:
Purchase requisitions
A requisition (regarded as an internal purchasing document) cannot be converted into a follow-on document until it has been released.
External purchasing docu. (RFQs, purchase orders, contracts, scheduling agreements and service entry sheets)
An external purchasing document cannot be issued to a vendor until it has been released.
Note:
Requisitions can be released either item-wise or in total. External purchasing documents can only be released in total.
Release Procedure for Purchase Requisitions:
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
Characteristics (CT04): In the classification system, characteristics describe the properties of objects. The values of a characteristic specify these properties.
Characteristic COLOR has the values 'red', 'green', and 'blue'. When you classify an object, you use this characteristic to specify the color of the object.
Steps:
1. Enter Character Name using Create button.
2. In Basic Data Screen - Enter Description, Status, No. of Characters & multiple Values.
3. Go to Additional Data Screen - Enter Table Name, Field Name then choose tick Not ready for I/P.
4. Go to Values Screen - Enter Char. Value & Description.
5. Go to Restriction Screen - Enter Class Type.
6. Then go to Additional Data Screen remove the Tick of Not ready for input & save.
Class (CL02): Group of characteristics that can be attributed to a product. A class is a grouping of similar objects according to common characteristics.
Class Type: A class type is a top-level unit of control for classes. Each class must be allocated to exactly one class type. There is no connection between the individual class types.
Steps:
1. Enter Class Name & Choose Class type then Create using button.
2. In Basic Data Screen - Enter Description & Status.
3. Then nothing will be entered in keywords & Texts screens.
4. In Characteristic Screen u2013 Enter created characteristic then save.
Set Up Procedure with Classification (OMGQ):
1. Then go to Set Up Procedure with Classification
a. Release Group - Enter two char. (or) no. for Release Group, Class & Description then save.
b. Release Code u2013 Enter release group, Code Workflow & Description.
c. Release Indicator u2013 Nothing to enter.
d. Release Strategy u2013 Enter Release Group, Release Strategy, and Release Codes.
Release Prerequisite u2013 Choose order of release.
(ii) Release Status u2013 give continue.
(iii) Classification u2013 Enter the Value of Characteristics Description.
(iv) Release Simulation u2013 Double click and activate.
e. Workflow
Release with Link to Workflow:
Use
When you set up the release procedure with classification for purchase requisitions or purchase orders, you can define a link to the SAP Business Workflow. This is particularly advisable if employees whose daily duties include tasks other than the approval of requisitions or purchase orders are involved in the release procedure.
Features
The employee is automatically advised when a release is to be effected. A work item appears in his or her inbox, which he or she can process directly. When the item is processed, the SAP release transaction is automatically invoked with the relevant release code.
Then do PR in that Release Strategy will appear in both Item Level & Header Level. After that go to Release approval for Purchasing Document (ME28).
Release Group - The multiple usage of the same release strategy key.
Release Code
Two-character identifier with which a person responsible for processing a document can release (approve) an item of a purchase requisition, a complete purchase requisition, or a complete external purchasing document, or cancel such release (that is, revoke a previously granted approval). If a link to SAP Business Workflow has been defined for the release code, the person involved can also refuse to effect release (withhold approval), thus rejecting the relevant item or document.
Release Indicator
Shows the release (approval) status of a purchasing document.
When you have released (approved) an internal or external purchasing document with your release code, a release indicator is assigned to this document. The release indicator determines how the document may be processed further. For example, it may show that a requisition can be converted into a purchase order, or that a subsequent release point (individual or department) must first signify approval.
Release Strategy
The release strategy defines the approval process for purchase requisitions or external purchasing documents. The strategy specifies the release codes necessary and the sequence in which releases have to be effected. You can define a maximum of eight release codes.
The assignment of the release strategy to a requisition or a purchasing document is based on the release conditions.
Release Prerequisite
Specifies the sequence in which the processors (members of staff responsible for processing a certain document) must approve an internal or external purchasing document with their respective release codes.
Example:
The release (approval) procedure for purchase requisitions within an enterprise may provide that a department manager must release (approve) a requisition item before the next-higher level of authority (for example, the cost center manager). In this case, approval by the department manager is the prerequisite for approval by the cost center manager.
Release Status
Displaying the Release Status
You can display the release status of all items of a purchase requisition or the Complete Purchase Requisition in an overview. The overview shows whether each item or requisition has been released or is blocked, etc.
1. Display the item overview for the relevant purchase requisition.
2. Choose Goto Release info Release status.
A dialog box providing information on release statuses appears.
Displaying the Release Strategy
To display details pertaining to the release of an item or a complete requisition, proceed as follows:
1. Display the item overview for the relevant purchase requisition.
2. Select an item.
3. Choose Goto Release info Release strategy.
A box appears, giving you the following information:
1. Description of the release strategy
2. Previously effected releases involving the purchase requisition
3. All release codes with which the requisition must be released before it can be converted into an RFQ or a PO (final release)
If alternative release codes have been defined, the different ways in which this requisition item can achieve final release are shown.
Regards,
Kiran

PO Workflow release

Similar Messages

Maybe you are looking for