Po release workflow remains in "In Process" state

Hi workflow Guru's,
The release strategy attached with PO requires 2 level of approval.( copied standard WF20000075 .).
when user creates PO nd saves the PO, workflow initiates to first level PO releasing with assignment of role.
When approver double clicks work-item he is taken to PO release screen and he can able to release the PO.
now as per sequence, work-item should now flow to 2 level approver whereas
work-item remains in "in process'
state in 1 level approvers inbox and workflow also remains in "In Process " state.
Please help me out sort this issue.
Regards,
Mohd.

Dear Abdul..
Try these 2 things,
1. Go to that particular step in workflow where you have done the binding for release code & click check icon to check whether binding for release code is error free... There are chances for your workflow to get activated but the binding in a particular step can contain errors.. So check this first..
2. You should be passing the release code value from workflow container to task container.. Check whether value is coming correctly in workflow container first.. I believe it will not come as part of standard workflow & you should have written your custom logic to fetch that.. If yes then thoroughly check your custom logic (In case of BOR method then execute that method individually in SWO1 & check whether values are coming correctly).. If the value of release code is coming correctly in workflow container & not in task container (you can check this by going to that particular step in SWI1 & see the container tab) then again go to SWDD & click check icon in binding for that step to see whether its error free..
I strongly feel that workflow is going into INPROCESS state because of this missing release code value..
Kindly check & let us know ..
Regards,
Bharath

Similar Messages

Workflow remainds in "In Process" state and doesn't flow ahead

I am facing a weird problem, there is one workflow having a fork step. The fork step is successfully executed, and after that there is another step for updation of z-table. that is not getting executed only. And workflow has stopped there and not flowing ahead. Has anyone faced such problem?
Edited by: sap_abap on May 22, 2009 9:31 AM

which method or task should i execute? the fork has two steps:
1. sending notification to approver for approving the Task in his UWL.
2. The UWL in the approver's Inbox
Both are executed, mail has reached the approver and he has also approved the request. After that fork ends, but workflow not going ahead.

Workflows remain in starting state

There is a production sharepoint site and qa sharepoint site. The workflows were made and tested in the qa site. I then made templates of all the list associated and added them to the production sharepoint site. After that I recreated all the workflows because
they were list workflows, and set them to go off when an item is created. However when ever an item is created all the workflows remain in a starting state and no amount of time changes it, for I still have a workflow starting from 2 days ago. What do I do
to resolve this problem? As well this will all made using SPD 2010 and sharepoint 2010

Hi,
see whether these links helps you -
http://blogs.msdn.com/b/chaun/archive/2013/05/16/if-your-sp2010-workflows-are-stuck-in-the-starting-state.aspx
http://social.technet.microsoft.com/Forums/sharepoint/en-US/5a6e6e83-b59f-4099-a86f-a07723ff2b98/workflow-stuck-in-starting-state-after-applying-sharepoint-2010-cu-december-2012?forum=sharepointadminprevious
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if my reply helps you

Background step in workflow remains in process: Workflow gets stuck up

Hi Gurus,
I have custom workflow for organization management. The workflow takes information from e-forms(notifications) and updates the infotypes.
The step which updates infotypes is run as background step.However in some cases the workflow gets stuck up in this step.
This happens irregularly (once or twice in a month).
On processing these workflow instances using SWPC , nothing happens and the workflow remains stuck up in the same step.
Also checked for dumps but nothing available under WF-BATCH.There is no regular pattern for occurance of these instances.
Can you please suggest what can be the possible cause of them getting stuck up in the background task.
Regards,
Rohit

Check ST22 shortdumps again. Look not only for WF-BATCH but also look for the intitator or the last processor's ID. Sometimes they would be the assigned the user to execute the step ecven if it's a background task.
Also, I would suggest looking through the code of the method that is being executed carefully. Make sure there are no 'EXIT' or LEAVE' statements. This could also 'sometimes' cause the background process not to return correctly. In addition, check that you are not executing an ever lasting loop.
If you have access in PRODUCTION, try to execute the method in debug mode to see where the program is inappropriately stopping (t-code SWO1).
Derrick
Banks & Company, LLC

Project server 2013 olap database remains in processing state

Hi,
In an attempt to restore the Reporting Database in Project Server 2013, I did an archive and restore of Custom fields. Both of these events were successful, however, the Reporting database refresh kept on hanging in "Waiting to be processed status".
Before this was noticed, the OLAP Database was configured and a build was initiated. Now the status of the PWAOLAPDatabase build just remains in the "Processing..." status. What am I to do here? Thanks!

Hi Jaco,
It seems like your reporting database refresh has failed, so the OLAP DB cannot be generated either. It could be due to a large resource pool.
See reference below:
http://social.technet.microsoft.com/Forums/projectserver/en-US/7ac3bb1b-6621-46f0-a6c5-d9a04f770418/reporting-database-refresh-project-server-2010?forum=projectserver2010general
http://blogs.msdn.com/b/brismith/archive/2011/07/14/project-server-2010-reporting-database-refresh-failing-with-large-resource-pools.aspx
Note also that you can click on "processing" (as per your screenshot) to have the OLAP DB creation log in order to have more information on the status.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Workflow task in "In Process"

Hi all,
I have a workflow task that stayed in the "In Process" state. The task's method calls a function. I don't know if the function had an error or what actually happened. The function makes a call to a third party software(PRISM). I have the task set to synchronous to wait for a return code. Does anyone know of a way to trouble shoot this.

Yes, if you can reproduce it by calling the same method with the same inputs from transaction SWO1 (testing the BOR object type - or SE24 if it is a class). Then the debugging should reveal most of the information you need.
I assume you are making an RFC call. In your function call you should, if it has not been done already, set up the special exceptions for RFC calls which will enable you to receive a returned error message in case of e.g. communications failure.

Vendor payments release workflow!!!

Hi all
Can somebody explain to me how we setup standard workflow so that all vendor invoices greater than 100.000 can be blocked for payment automatically & released by some other user?
I tried to give the document type "KR" to the workflow variant & tried to do invoicing for the vendor. But I do not how I could release that blocked invoice...Is there any specific tcode or I have to go to the proposal & change the blocked reason from P to 'space'.
Thanks for all your time....

Hello Morgan,
Payment Release Process
Purpose
For each workflow variant, you can specify the amount from which a payment release should be triggered.
You can differentiate between one, two, and three-level release. This enables between one and three people to be involved in the release procedure, thus supporting both dual and triple control.
Prerequisites
You have made the following settings in Customizing:
Release approval procedure
(document type and amount for each workflow variant)
Assign persons with release authorization
In order to do this, you must first create release approval groups that can be entered in the customer and vendor master records.
Depending on these criteria and the release level, you can assign release authorizations in the form of organizational objects (job, position, organizational unit) in Customizing. If you do not define any criteria (such as release approval groups), the system takes the initial value of these criteria when the payment program is run. For example, if the system was unable to determine the release approval group, the release approval procedure and the employees with release authorization are determined on the basis of release approval group zero.
Process Flow
Minimum requirements:
The payment release function must be activated.
The relevant document type must be defined.
An item containing the following specifications must be created for employees with release authorization:
Workflow variant
Initial release approval path
Initial level
Maximum amount
Employees with release authorization can also be determined and assigned by user exits at each stage of the release approval procedure.
Result
If, when the payment run is made, the system could not determine an employee with release authorization, then it sends a message to the inbox of every person who has been assigned the task "payment release". Only after all these people have released the payment will the payment block be removed.
If a line item is refused for release, it is forwarded to the clerk who entered it for correction. After the document has been changed, the payment release procedure begins again. If changing the line items necessitates further actions, these must be defined within the Workflow component. The event CHANGED has been preconfigured for this purpose in the standard workflow model. If you run this event, the system assumes that the line item was rejected for payment. However, the item is NOT forwarded for correction to the clerk who entered it.
If an item is cleared before it is released, the payment release procedure is terminated (event CLEARED).
===========================================================
Workflow settings: The standard system contains several workflow models for payment release: One workflow framework (WS00400012) and three sub-workflows. In Customizing for Financial Accounting, you can specify which sub-workflow should be used when the workflow framework is run. You can also enter your own sub-workflows. They must however send and receive the same data from the workflow framework as the workflow models do.
You can use the standard sub-workflows (WS00400011, WS00400021, and WS00400022) to carry out a one, two, or three-level payment release procedure. If you require more than three release levels, you can copy the workflow models, enhance them and then enter the enhanced workflow definition in Customizing for Financial Accounting.
Event Linkage for the Event CREATED
If an amount requires a payment release, the event CREATED is triggered when a document is posted.
In this case, you must go into the workflow framework in the Workflow Workbench and enter the event linkage for this event, as described below:
Data for Event Linkage
Object type
BSEG
Event
CREATED
Receiver type
WS00400012
Receiver module
SWW_WI_CREATE_VIA_EVENT
Check Function
Receiver type
FM (function module)
Global
X
Enabled
X
Standard Tasks for the Event CREATED
The standard system contains two standard tasks that are triggered from the workflow mailbox and used in the workflow models.
Payment release (line item)
Change (line item)
Creating and Assigning Organizational Objects for Payment Release
You must assign organizational objects (organizational units, jobs, positions) to the standard tasks. These organizational objects can be created either in Personnel Planning and Development, via the Workflow Workbench, or in Customizing for Financial Accounting (assignment of release authorization to employees).
When you create organizational units, you must assign them to jobs or positions. You can then assign users to the positions.
Examples for assignments:
Organizational unit X < Position Y < User
Organizational unit X < Job Y < Position Z < User
In Customizing for Financial Accounting, you can assign organizational objects to the workflow variant, the release approval path, the release approval level, and the amount. These objects then release the amount depending on these criteria.
The organizational objects for payment release defined in Customizing for Financial Accounting are automatically assigned in the background to the standard payment release task (TS00407862).
The organizational objects for changing line items after they have been rejected for payment must be assigned to the standard task "Change line item" (TS00407864), either in Personnel Planning and Development, or via the Workflow Workbench. Alternatively, you can define the task as a general task (Additional data -> Classification).
Changing Line Items
The workflow models described above all contain a pre-configured event (CHANGED), which triggers other events in the same fashion as a rejection does. This event can be triggered by change documents. You must define it via the Workflow Workbench.
Hope I had been able to help you. Please assign points.
Rgds
Manish

Getting two same workitems in PO release workflow for 2 level

Hi experts,
I am working in PO Release workflow upto two level of release.
But while triggring my workflow by creating PO I get two same workitem.One of the two has correct Release Code(I have checked that in workflow log) and another has Release Code with no value.If I execute one of them Its working fine.But 2nd one still remains in inbox.I think my workflow has been triggred twice while I am creating a PO.
Can someone suggest, where is the problem?
Thanks,
Manas

Hi,
According to your instruction I have got 5 event trace.
BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
QCYBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
BUS2011     QUOTATIONCREATED     14.02.2008     16:31:57          @AI@     No receiver entered
BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
FREBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
I have given you the details of the event traces.
Here I notice RELEASESTEPCREATED event occurs twice.
Can you please suggest why this is happening?
Thanks,
Manas.

Payment release workflow thru F-53 Transaction help needed

Hi gurus,
I am trying for payment release workflow using F-53 which is the client requirement. As there is no parking option in the transaction i created a custom event "parked" in the transaction .I tried using BTE. but i m not able to find the right product no in infosystems of BTE for the transaction F-53. Is there any way for payment approval workflow.
Thanks and Regards,
Kumar

Hi Kumar,
Actually, what you may do is setup a workflow for automatic payment with approval/rejection process which would trigger a BAPI for f-53 process.
And keep the below items in mind before finalize:
a. F110 will not clear any blocked invoices.
This is the default setting, as a security for the blocked items stay in the system
(blocks are always there with a reason).
b. In F-53 you can control what you want to clear (not automatic),
therefore some blocks can be redefined allowing F-53 to clear SPECIAL-BLOCKED items
You may find more options too.
Thanks
MKS

PO Processing State

Dear All,
Can u tell me all the States of PO Processing as
Purchasing document processing state    03
here what it Mean by 03.
Please help me
Regards,
Pardeep malik

Dear,
The system always creates a new version when the purchasing document has reached a final state.
This means one of the following processing states:
●     Active
If you do not use the document release functionality
●     Release completed
If you use the document release functionality
For a new version of a purchasing document to be created, all messages must have also been transmitted.
No new versions are generated for purchase orders that are on hold.
Not every change to an external purchasing document results in a new version. The following changes lead to a new version:
●     All print-relevant changes
You define which changes are print-relevant in Customizing for Purchasing under Messages ® Fields Relevant to Printouts of Changes.
●     Changes in document assignment
●     Changes in address
Address changes result in a new version only if the field ADRC-NAME1 has been defined as a field that is relevant to printouts of changes.
●     Changes to master conditions
Changes in master conditions result in a new version only if the field EKPO-NETPR has been defined as a field that is relevant to printouts of changes.
Version Data
You will find the version data:
●     In the item details on the Versions tab page in Enjoy purchase requisitions (ME51N, ME52N, ME53N)
●     In the header data on the Versions tab page of Enjoy purchase orders (ME21N, ME22N, ME23N)
●     Under Header ® Versions in RFQs, conventional purchase orders (ME21, ME22, ME23), contracts, and scheduling agreements.
There you can maintain version data (e.g. reason for change) and complete the version. In addition, the Value change field shows you whether and to what extent the value of a requisition or external purchasing document item has changed in comparison with the previous version.
You can display the change documents for one or more versions by selecting the relevant versions and choosing Display Changes.
Please check accordingly.
Regards,
Syed Hussain.

PR overall release workflow

Hi All,
I am working on PR overall release workflow (WS20000077) and had activated workflow for PR rejection 'wf_pur_rejo' (WS65400029). When i create a PR using ME51N workitem gets created. When we reject the PR by executing the workitem i receive the workitem for rejection also. Everything is fine till here.
But when i try to execute the workitem (Purchase Requisition XXXXX Rejected) i get an <b>error 'No Administrator found for the task'</b> and i observed that in workitem log it is shown in READY STATE. This happens for some user ids and it works fine with some other user ids.
Can any please tell me where i am going wrong and if i am then eloborate on what should i be doing?
Thanks in advance,
Regards,
Lakshmi Narayana.S

I have got it, ran the Transaction SWU_OBUF to synchronize the buffers and re-logged into SAP. Now the problem is solved.
Regards,
Lakshmi Narayana.S

Error in PO release workflow

Hi all,
I'm having problem with linkages errors when I active PO release workflow WS20000075. The wf work without problem in develop system but in the system where I transport, a internal message is sent to me with text:
Error in event receiver
Error processing following event linkage:
BUS2012 RELEASESTEPCREATED WS20000075
Following error occurred:
SWF_RUN 594
Message text:
Import container contains errors (are any obligatory elements missing?)
Event container appended as attachment.
Event linkage with errors deactivated.
The customizing is the same in both system and I don't understand the problem.
Thanks in advance.

I think you might have missed the binding between the event container adn workflow conatiner try to co like below.
1. OPen the workflow template WS20000075 open in change mode , click on the tab Triggering Events slect the entry which you are able to see on the screen .
2. Click on the binding button, and do the following entries.
&_EVT_OBJECT&          &PURCHASEORDER&
&RELEASECODE&          &RELEASECODE&
&_EVT_CREATOR&          &_WF_INITIATOR&

Callbacks for Process States

Hi all,
Are there any callbacks available for Process states(faulted,closed,completed) etc similar to callbacks for human workflow tasks in BPEL 1013? I need to handle the scenarios when a process is faulted or is aborted (from BPELConsole) and propagate this information to my application.
thanks,
Ravikiran

This is normal exception handling. You just use the Fault handling in the SOAP response.
Create a Fault message in your BPEL process and send this back to the client.

1.How to release workflow ?

Hi friends,
1.How to release workflow ?
Please give the details of release process & type of release !
Thanking you.
Subash

Hi,
I believe that, you created a Workflow that you want to Transport to QA & PRD, right.
The Workflow Template will store in the Workbench Request and event mapping & the activation will stored in the customizing Request.
While Creating & Activating the workflow itself this will ask for a Transport Request.
Then you have release the both request.
First move Workbench, then customizing Request.
Regards,
Surjith

BPEL process state "Off"

Hi,
I had created one BPEL process which reads from FTP Remote server and writes to local file directory.
After reading from Remote FTP server I am deleting file from the server. In the remote server I had created on user to interact with FTP server with all permissions. When the BPEL process executed FTP Adapter is deleting the File successfully from remote location but BPEL state is changed to “Off”.
When I checked the logs, I found there is problem with Delete permission. Actually as mentioned above file is deleted successfully in the remote location.
OPMN logs:
<File Adapter::Outbound> Processing file : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt
<File Adapter::Outbound> Sending message to Adapter Framework for posting to BPEL engine: {
file=/click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt
<2007-06-11 19:00:42,677> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process FTPRetrieveTOFileWriteProcess, revision 1.0 needs to be reloaded
<2007-06-11 19:00:42,709> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at http://dt1521-localhost.com:80/orabpel/default/FTPRetrieveTOFileWriteProcess/1.0/_FTPRetrieveTOFileWriteProcess.wsdl
<2007-06-11 19:00:42,709> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at: http://dt1521-localhost.com:80/orabpel/default/FTPRetrieveTOFileWriteProcess/1.0/_FTPRetrieveTOFileWriteProcess.wsdl
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Sucessfully sent message : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt to Adapter Framework.
<2007-06-11 19:00:42,724> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Deleting file : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt after processing.
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host name is 'DT1521-localhost.com'.
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Reading reply from DT1521-localhost.com
<2007-06-11 19:00:42,818> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: Write, partnerLink: <partnerLink name="FileWriter" partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_plt">
<myRole name="null">
<ServiceName>null</ServiceName>
<PortType>null</PortType>
<Address>null</Address>
</myRole>
<partnerRole name="Write_role">
<ServiceName>null</ServiceName>
<PortType>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_ptt</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/10610-BpInv1-BpSeq1.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at D:\OraHome_1\integration\orabpel\domains\default\tmp\.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar\Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at: D:\OraHome_1\integration\orabpel\domains\default\tmp\.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar\Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=Write, parnterLink=<partnerLink name="FileWriter" partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_plt">
<myRole name="null">
<ServiceName>null</ServiceName>
<PortType>null</PortType>
<Address>null</Address>
</myRole>
<partnerRole name="Write_role">
<ServiceName>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write</ServiceName>
<PortType>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_ptt</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/10610-BpInv1-BpSeq1.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::doShortCut> Parner Property optShortCut
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> ResourceAdapterMetaData Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl [ Write_ptt::Write(opaque) ] - Looking up Resource Adapter JDNI location 'eis/FileAdapter'
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Managed Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Creating Connection
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Creating FileInteraction
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> FileInteraction Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec with properties: {FileNamingConvention=spob230_%SEQ%.txt, OpaqueSchema=true, ElapsedTime=60, NumberMessages=1, PhysicalDirectory=c:\inbound_dir, FileSize=1024000}
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/fileAdapterOutboundHeader.wsdl
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/fileAdapterOutboundHeader.wsdl
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl [ Write_ptt::Write(opaque) ] - Invoking JCA outbound Interaction
<2007-06-11 19:00:42,849> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> File Adapter received an input Record
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Waiting outside sync object.....
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batcher created using staging : true with number of messages : 1
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Input Record: javax.xml.transform.dom.DOMSource@e5394c
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Translating....
<2007-06-11 19:00:42,849> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Outbound Translation done.
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Refreshed (staging/num Messages) file count : 1
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: USER orabpel
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Wrote to Control File
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batching staging File: staging0
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batcher sending to sender for output file writing
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Sending File to output Dir
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FileAgent.putFile() puts spob230_17.txt in c:\inbound_dir begins ...
<2007-06-11 19:00:42,865> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Done Writing to output file spob230_17.txt in dir c:\inbound_dir !!
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> End clearing Control File
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Deleting staging File: staging0
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> End clearing Control File
<2007-06-11 19:00:42,881> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Interaction gets a ok response
<2007-06-11 19:00:42,881> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Done with Input Record
<2007-06-11 19:00:43,256> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: USER, reply:
331 Password required for orabpel
<2007-06-11 19:00:43,256> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: PASS
<2007-06-11 19:00:43,506> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: PASS, reply:
230 Login OK
<2007-06-11 19:00:43,506> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: CWD /click/xelusparts/feeds/jabilparts/outbound/process/
<2007-06-11 19:00:43,615> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: CWD, reply:
250 Directory successfully changed
<2007-06-11 19:00:43,615> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: DELE po_28.txt
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: DELE, reply:
200 Deleted file "po_28.txt".
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTPClient.deleteFile(): 200 Deleted file "po_28.txt".
<2007-06-11 19:00:43,709> <ERROR> <default.collaxa.cube.ws> <File Adapter::Outbound> FTPClient.deleteFile(): Unable to delete file po_28.txt', reply code = 200
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Processer thread calling onFatalError with exception Error deleting file from FTP Server.
Unable to delete file from server.
Please ensure whether the remote file has delete permission.
<2007-06-11 19:00:43,709> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Get_ptt::Get(opaque)] - Resource Adapter requested Process shutdown!
<2007-06-11 19:00:43,709> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactivation for portType=Get_ptt, operation=Get
<2007-06-11 19:00:43,709> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Endpoint De-activation called in adapter for endpoint : /click/xelusparts/feeds/jabilparts/outbound/process/
<2007-06-11 19:00:43,725> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process FTPRetrieveTOFileWriteProcess, revision 1.0 needs to be reloaded
<2007-06-11 19:00:44,037> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::onStateChanged State is changed for process 'bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/', state=OFF
<2007-06-11 19:00:44,037> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::updateRevision> Updated state for process FTPRetrieveTOFileWriteProcess (revision 1.0) to 1
Thanks,
Vidya

Hi SR,
You can do this by having a BPEL process with a java embedding containing below code.
* Input Variables
String processName   = (String)getVariableData("processName");
String revision      = (String)getVariableData("revision");
* Declare variables.
IBPELProcessHandle procHandle = null;
Locator loc = null;
BPELProcessMetaData bpelProcessMetadata = null;
try{
     * get Locator Instance
    loc = getLocator();
     * Lookup Process. Revision optional.
    if(revision == null || revision.trim().equals(""))
      procHandle = loc.lookupProcess( processName );
    else
      procHandle = loc.lookupProcess(processName, revision);
    if(procHandle == null)
      throw new Exception("Unable to find process: " + processName);
     * Get Metadata of the process.
    bpelProcessMetadata = procHandle.getMetaData();
     * Set Lifecycle to Retired.
     * Use setState(IBPELProcessConstants.STATE_OFF) to change process state to off.
    bpelProcessMetadata.setLifecycle(IBPELProcessConstants.LIFECYCLE_RETIRED);
     * Finally update the process with the modified metadata.
    procHandle.updateMetaData(bpelProcessMetadata);
}catch (Exception e)
addAuditTrailEntry(e);
}If you want you can schedule this process.
Regards
PavanKumar.M

Po release workflow remains in "In Process" state

Similar Messages

Maybe you are looking for