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

Similar Messages

How to control PO Release strategy using WorkFlow

please tell me how to control PO Release strategy using WorkFlow.
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on May 31, 2011 9:35 AM

Hi,
Yes they are same unless you differentiate by using
1> Purchasing Document Category i.e CEKKO -BSTYP
A..... Request for Quotation
F......Purchase Order
K......Contract
L......Scheduling Agreement
So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

How to avoid po release strategy replicating in RFQ

Dear Sapiens,
I am aware as we are using same class for PO RFQ and Contract the release strategy will repliacte in rest,
but I dont want PO release strategy to get repliacted in RFQ,because I dont have realease for RFQ
how to avoid po release strategy replicating in RFQ?
Regards
Kantha

Hi,
Yes they are same unless you differentiate by using
1> Purchasing Document Category i.e CEKKO -BSTYP
A..... Request for Quotation
F......Purchase Order
K......Contract
L......Scheduling Agreement
So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

How to turn off Release strategy

Hi,
We need to upload purchase orders via LSMW. While doing so, we do not wan the release strategy to be active to avoid the need for approving each order. How can I turn off the release strategy.
Thanks in Advance.
Regards,
Pavan

Hi
Not sure if this requirement is to handle the cutover POs/ POs which were already approved in legacy system, I have handled this by two ways in the past ( as due to last minute changes we were not sure abiut frequency and need of turning release strategy to on / off
1. We have use a charactertistc (corressponding to PO date ) in Rel strategy and setup in such a way that REL strategy is active for PO with PO date > Go-live date ( all legacy POs were loaded with s date earlier than Go -live date)- this ensure that we need not to do on/off several time
2. another case we created a seperate PO doc type and excluded from rel strategy, no uses was given authorization for creation of this except the cutover / data migration team which was responsible for cutover
Hope these suggestion helps
Reg
Dheeraj

How to Display PO Release Strategy in Enjoy Screen

Dear all,
I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
Thanks a lot.

Thanks 4 the reply Rahul.
I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
Thanks and appreciate if anyone could help.

How to set the Release Strategy without classification for PR

Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh

1. Release codes
   Create the release codes.     For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
   Define release indicators and branch to the detail screen. Here you
   define whether fixed purchase requisitions may be changed by Materials
   Planning, for example, and whether an RFQ or a purchase order may be
   created from the requisition.
   You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
   specify whether a requisition may be changed after the release
   procedure has begun. You specify whether the strategy has to be
   redetermined after changes, or whether the release procedure has to
   start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
   example, previous releases are not cancelled if the value of the
   requisition item after the change does not exceed plus 10% of its
   original value.
Attention:
   Be sure to create a release indicator (e.g. B for "blocked") that
   serves as the starting point for subsequent indicators. Do not set the
   indicators for release for the issue of RFQs and PO on the detail
   screen for this indicator.
   Also create a release indicator characterizing the released status.
   Set the indicators for release for the issue of RFQs and PO on the
   detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
   Assign a release indicator in dependence on the status of the release.
Example:
   You create a release strategy S1 consisting of two release codes 01
   and 02. Release with 01 is a prerequisite for release with 02. If
   release has been effected with 01, the requisition has been given the
   "all clear" for the issue of RFQs.
   You have created the release indicators B (blocked), 1 (cleared for
   issue of RFQs) and 2 (cleared for RFQs and PO).
   Now enter the following as assignment:
Strategy   C1 C2 C3 ...
   S1                          B (blocked)
   S1         X                1 (RFQ)
   S1         X   X            2 (RFQ/PO)
4. Release prerequisites
   Define which release codes are involved in a release strategy. Specify
   whether a code is set for a release status following release, and
   whether one release status is a prerequisite for another (+).
   Example:
Strategy   Code C1 C2 C3 ...
S1         01    X
S1         02    +   X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

HOW TO BLOCK A RELEASE STRATEGY

Sir,
ply help me in blocking a release strategy as in i want to configure a new strategy
ply help
regards
amey

hi,
You can do the blocking of current release strategy via:
removing the connection of the release group to the release class and then deleting the release strategy parameters inside the release strategy tab under spro settings ...
Paul,
If we only remove the characteristics, system also determines internally,,, then will it be deactivated??
Regards
Priyanka.P
Edited by: Priyanka Paltanwale on Apr 27, 2009 4:52 PM

How to retrigger PO release strategy

Hi all,
We have configured PO release strategy. When creating PO, it is initially blocked. Then the manager have to release. When the PO price is increased, the PO will again be blocked. When the price is decreased, the PO is saved without any block. The requirement is to use the same logic when the price is increased and decreased. That is, to block the PO.
Kindly let me know if this is feasible.
Thank you.
Nene

Hi,
You should check first of all with your MM consultant see if through configuration is possible. If its not possible, you could use an user exit when saving, and check if price changed, and reset the release code using the bapi BAPI_PO_RESET_RELEASE.
Regards,
Gilberto Li

CCreate Release Strategy using department name in "Release Code", not User ID SAP.

hi experts...
i wanna create new release strategy, but in part "choose activities => Workflow => assignment of role to release code"
in field Agent ID usually we fill SAP user ID, but i wanna using department name.
is there anyone can help me
thanks,

Hi Raju,
Are you setting release for purchase requisition or purchase order ? If you are setting the release strategy for purchase requisition you need to enter table name as CEBAN and for purchase order give table name as CEKKO.
Enter tcode SE11 and give database table name as CEKKO and choose the appropriate field name for the desired component from here. Do the same with table name CEBAN for pur req.
Hope this was helpful.
Cheers,
XsNitin

How to Reject RFQ (Release Strategy)

Hi,
In ME29N , we have facility to Reject / Approve a Purchase order in Release staretgy tab .... but how to reject a RFQ .
There is no option available in ME45 to Reject a RFQ, only we can release it.
Need your help
REGARDS
SHREY

hi
rejection of rfq is not possible
ru talking of calcelling or reversing the release
if yes
then in me45 select therel code then belowt that tick on cancel release
execute ,select ur po and click on cancel release
regards
kunal

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

How to attach event to custome workflow object ?

Hi Guys,
Could someone help me on how to raise event while creating custom workflow object.We can attach event to object in transaction swe2 . I would like to know how to create that event. Could some send sample custom workflow object with events.
Many thanks in advance.
Cheers,
Garrick.

Here's an example using Business object BUS2080 Service notification
I delegated ZBUS2080 to BUS2080 (service notification). Added 2 Events REASSIGNED and MODIFIED.
Use transaction SWO1 for manipulating business objects.
The User performs an action on a service notification (IW52) say PUT IN SERVICE AGAIN.
When the user puts the service notification in service again the event triggered will start a (user defined) workflow which makes a call to a method in the business object ZBUS2080 which launches a batch job.
This batch job creates our user event REASSIGNED which in turn calls a new workflow to be executed.
This workflow performs the action I want -- in this case to re-assign the service notification to a new person, send an email and escalate the deadlines
Code samples are shown below.
So here's how it works.
First you need to set up some entries with table SWE2. I've assumed you've already defined the events to the Business object(s) you want to use.
In SWE2 define entries for BUS2080 (or ZBUS2080) For Events INPROCESSAGAIN and (our event) REASSIGNED.
IN SWE2 define the receiver call as a FUNCTION MODULE
For the receiver function modules for the SAP event (INPROCESSAGAIN) define the receiver module as SWW_WI_CREATE_VIA_EVENT
For the event REASSIGNED define the receiver module as SWW_WI_CREATE_VIA_EVENT_IBF.
I have no idea whatwhat the difference is between the two but the process works when it's done like this.
Ensure the linkage Activated box is clicked in both cases.
Put your workflow numbers in the RECEIVER TYPE in SWE2 table.
In the first workflow when the user puts the service notification in service ensure your workflow starts a batch job which raises another event
Note : You need to instantiate the object (I.e supply the key) to trigger the event correctly. The key is obtained from the WF and will be in the container anyway.
You can do this by adding this type of function module into the method of the business object you want to execute during the first workflow. The code here creates a batch job which submits the EVENT creating program.
function z_create_event_for_cs.
""Local interface:
*" IMPORTING
*"     REFERENCE(OBJECT_KEY) LIKE SWOTOBJID-OBJKEY
*"     REFERENCE(W_REASON) LIKE HRPXXXX-DUMMY
*"     REFERENCE(W_ESCLEVEL) LIKE HRPXXXX-DUMMY
Create Batch job to run ZZREASSIGNCS
which creates event REASSIGNED in Customer query workflow.
data: jobnr like tbtcjob-jobcount,
      jobname like tbtcjob-jobname,
      pgmname like sy-repid,
      w_key like viqmel-qmnum,
      w_code type c,
      w_num type c.
      w_num = w_esclevel.
      jobname = 'CREATEEVENT'.
    pgmname = 'ZZREASSIGNCS'.
call function 'JOB_OPEN'
exporting
    jobname                = jobname
importing
   jobcount               = jobnr
CHANGING
RET                    =
exceptions
   cant_create_job        = 1
   invalid_job_data       = 2
   jobname_missing        = 3
   others                 = 4
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
input = object_key
importing
output = w_key.
w_code = w_reason.
if w_code = ' '.
w_code = 'Z'.
endif.
submit zzreassigncs
with p_key = w_key
with p_escl = w_code
with p_escnum = w_num
via job jobname number jobnr
and return.
call function 'JOB_CLOSE'
exporting
     jobcount                          = jobnr
     jobname                           = jobname
   strtimmed                         = 'X'
exceptions
    cant_start_immediate              = 1
   invalid_startdate                 = 2
   jobname_missing                   = 3
   job_close_failed                  = 4
   job_nosteps                       = 5
   job_notex                         = 6
   lock_failed                       = 7
   invalid_target                    = 8
   others                            = 9
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endfunction.
For the actual program which creates the event use something like this
program zzreassigncs.
This program creates an event REASSIGN
This triggers a "clone" of the initial customer query workflow
which is now marked as completed.
The deadline and escalation level from the original workflow
should be passed to the new workflow via the event container
Program is submitted from the original workflow
Ensure transaction SWE2 has the event REASSIGN for bus object BUS2080
defined or the WF won't start even if the event is raised correctly
As this program is run as a background / batch task
you need to obtain the relevant notification number and pass it
as a parameter.
When run from the WF the you can get the notification number obtained
from the workflow / task container.
include <cntn01>.   "For WF macros.
parameters: p_key like swotobjid-objkey, "Service notification number
            p_escl type c,
            p_escnum type c.
constants: c_event    like swetypecou-event   value 'REASSIGNED',
           c_attrib   like swotra-attribute   value 'USRSTATUS',
           c_object   like swetypecou-objtype value 'BUS2080'.
data:     w_object like swotobjid,
          w_stat     like tj30t-txt04.
data: rc like sy-subrc.
data: begin of event_cont occurs 0.
      include structure swr_cont.
data: end of event_cont.
data: begin of return.
include structure swotreturn.
data end of return.
if running from WF rather than a batch job
swc_container container.
swc_get_element container 'Znumber' p_key.
w_object-objkey = p_key.
w_object-objtype = 'BUS2080'.
call function 'SWO_PROPERTY_GET'
exporting
    object                = w_object
    attribute             = c_attrib
changing
    value                 = return.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
w_stat = return(4).
event_cont-element = 'Status'.
event_cont-value = w_stat.
append event_cont.
event_cont-element = 'Escalated'.
event_cont-value = p_escl.
append event_cont.
event_cont-element = 'Escalation'.
event_cont-value = p_escnum.
append event_cont.
Note WAPI calls only valid from rel 6.1 using Webflow engine
(part of standard WF since rel 6.1)
CALL FUNCTION 'SAP_WAPI_CREATE_EVENT'
EXPORTING
    OBJECT_TYPE           =   w_object-objtype
    OBJECT_KEY            =   w_object-objkey
    EVENT                 =   'REASSIGNED'
IMPORTING
   RETURN_CODE           = rc
EVENT_ID              =
TABLES
   INPUT_CONTAINER       = event_cont.
if rc <> 0.   "Houston ---We have a problem !! '
write: text-002 color col_negative.
exit.
endif.
even though no database / table is updated here by the event
we still need the commit work to initiate the event correctly
commit work.
You CAN use Objects (OO ABAP) but if you are fairly new to this sort of stuff just stick with standard BOR (Business objects) to parctice on until you've got the hang of the process.
It's actually a lot simpler than most people realize --which is why WF consultants get paid decently !!!!.
Cheers
Jimbo

Re: Cancelling of approval in standard SAP release strategy.

Hello All,
At present the release strategy used by our client has the standard SAP strategy. The release strategy works fine for the approval part. The issue lies with withdrawal of approval.
At present when a lower level approver withdraws his approval, higher level approvals are withdrawn automatically. Our client requires that when a higher level approver has approved the doc, the lower level approver ( who has already approved the doc) should not be able to withdraw it.
i have looked around on SAP but i don't believe that standard SAP allows for a strategy for withdrawal of release. I believe this is a common requirement for many businesses. Could you please show me how to go about this. Should it be done through customizing. We do have a workflow in place.
If your business had the same requirement, how did you configure.
Thanks for reading this.
Regards,
Soumyadeep Paul

Hi,
I think you have configured you release matrix in such way that even higher level approver is dependent on the approval of the lower level approver.
In release prerequisite, don't set lower level approver's approval as a prerequisite for approval of higher level approver and then check. But this should be first discussed with the Business users and then only can be implemented.

How can Change PO Release Indicator to Released Status

Hi Gurus,
We are having an issue here, which user accidentally re-triggered customized program to re-trigger the release strategy of old PO documents.
This program basically reset the PO release startegy status and update the PO with the latest PO release strategy configuration. It's using FM ME_REL_STRATEGIE_EKKO.
So, currently some of the old PO which previously been fully released and closed PO (with GR & IR completed). So, we dont think that it's right for these old PO to be approved again, also the relevant approvers also refused to do so.
Is there any way that we can use the same FM to change the release indicator to R from S? Appreciate your help. Thanks!
Regards,
Michelle

may i suggest you accidently trigger the program to close the release strategy for all POs by modify class characteristics.
and then reopen the release strategy for necessary POs.
or maybe, you can trigger the program to close the release strategy for old POs.
please see below for details:
How to turn off Release strategy
Edited by: JiQing Zhao on Jun 14, 2011 1:19 PM

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

Similar Messages

Maybe you are looking for