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.

Similar Messages

Sap release strategy

dear gurus,
             I have created a release strategy. it is working fine. if i edit it in such a manner, that the po value increases, it goes for re-releasing. but the issue is, if i edit it in such a manner that the PO Value decreases it does not go fo re-release.
              so my requirement is that, if the PO value goes down it should go for re-releasing
thanks
ujwal

Hi,
please see the note 662993 Resetting an already occurred release.
"When you reduce quantities or values the system only resets the release
if another release strategy is determined for the lower quantity or the
lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
This is a standard functionality and is desired.
A change of this functionality is only possible by means of a
customer-specific modification."
In standard there is no customizing setting to change this behaviour.
You need to use userexit EXIT_SAPLEBND_002 or modify
the standard function module ME_REL_STRATEGIE_EKKO for this.
Regards,
Edit

SAP - Release strategy Characteristics Default Value Usage

Hi,
I am currently working on Release strategy where in I wanted to set the Default Values for the Characteristics. However, Even though I have flagged the Default values, system it is not defaulting the same.
Secondly, I tried to use Option CL20N Where the value are apper, but when I Save, It is not stored.
I wanted to know, Is there any setup need to be done for default value or is some thing I am Missing out.
Please Let me know ASAP
regards
Arvind

Maintain the default values in char itself.
Goto CT04 enter your char and in Value tab enter all your default values which will be defaulted while char selection in release startegy.
Note untill the char values are not checked during assigning class and release startegy in CL24N they will not be saved.

Release Strategy Processor Names under Release Strategy tab for a PReq

Hello Experts,
We have situation in Release Strategy for Purchase Requsitions in which we need to display all approvers names under the Release strategy tab for a Purchase Requisition.
Senerio work as follows.
Based on the Release strategy customization settings,Purchase Requisition subjected to release strategy selects the approver names from a custom table.
In the Custom table we have names of the approvers with release codes.
Purchase Requisition displaying the names of the approvers according to alphabetical order.Hence it displays First one user or approver name under the release strategy according to the approver alphabetical order from the custom table.
Can we display name of all approvers in one line according to initial investigation there is room for 40 characters under the release strategy tab.
Let me know if any Standarad OSS notes available for this.
Amogh

Hi amogh if you configure with workflow the strategy and the name of the persons are in transaction SU01, you don´t need to put nothing. The release strategy shows the names of the persons that release the document, but if you change one person in the release strategy, the system don´t save history for this, all old documents that have been released for this person, release strategy is blank. You have to do a non standard report that shows what person releases what document.
I hope that this information help you
Rose

ME54N Release strategy question over delivery tolerance limits

I set up a release strategy base on the over delivery tolerance level. My problem is when a Purchase requisition is saved as rejected, and i click on the button cancel reject it deletes the last release strategy level because now it is looking at the actual total value disregarding the over delivery tolerance level.
It works fine when the Purchase requisition is not rejected, and i can cancel or reject the purchase requisition without saving it and it does not delete the last line of the release strategy taking into account the over delivery tolerance level. I am using the user exit ZXM06U13.
Can someone give me some insight into this ? Thanks.

Hi Siva:
You should request the development key for this structure under your SAP system, then you can add the extra fields in CEKKO.
Good luck
Z.T

Release Strategy for Plants

Dearest Friends,
we have Plant A & Plant B
for Plant A     PR and PO <50K will be released by R1   and value >50K   by R1 and R2, R3.
*for Plant B   PR and PO >50K will be released by R1, S1 and >50K R1, S1, R2, R3.
how can we define the above release strategy.
hope you guys will help me.
Thanks and Best Regards,
Rajesh G

Hi,
for Release streagty either for PR or PO.
Steps :-
1. Create a Class T code CL01....Put Class type "32".
2. Crate Charateristics CT04 for ur case
Suppose for Plant ....in Addidtional data Put Table Name CEKKO and Field Name - WERKS
For Value ......... maintain CEKKO - GNETW
For PR .....
Table Name CEBAN --- WERKS for Plant
                      CEBAN -- GSWRT for Value
either go to se11, give the table name....u will get all the field there for which u want ur charterstics will work.
3. Assign Charcatristic to Class either in CL01 or cl24n.
3. Now go to Spro --> MM --> Purchase ---> release streatgy
first define Release code as R1, S1, R2, R3
Define GRp and Streatgy....
for Plant A PR and PO <50K will be released by R1
Suppose Grp is XY and Release Ste R1....click on details ....fill release Code R1 and in classification maintain Values <=50 and plant A.
Similarly Mainatin other....
Also u can document from
http://sapdocs.info/wp-content/uploads/2009/07/Step-by-step-guide-of-SAP-PR-Release-Strategy-configuration-a-case-study.pdf
http://sapdocs.info/sap/materials-management-2/automating-purchasing-approval-sap-release-strategy-tips/
Hope Help U !
Regards,
Pardeep malik
Edited by: Pardeep Malik on Sep 19, 2009 11:53 AM

User exit for Release Strategy in PM Work Order

Dear all,
Please help me with the following issue:
My client want to change the approval route of the release strategy of the Work Order. The release is based on the PM Activity Type. Now, I am brand new on the project, I have no documentation and I have no access to CMOD so I don't know where to find the cusomised release strategy for change it.
Please, can you advise on this?
Thank you very much.
Sorin

Dear,
to have release strategy based on "PM ACTIVITY TYPE", i suggest you two ways
Option-1:
1) Have permit system with classification as per the approval hierarchy.Create permits as per approval levels.
2) Once maintenance order is created, system will assign the permits to that maintenance order at the time of saving.
3) Now approvers will approve the permit with respect to Maintenance order PM activity type.
Note: If your client wants to have mailing functionality to their out look or other mails, put logic in save exit after assignment of permits to maintenance order, with the help of ABAPER and also the sequence of approving the permits.
Option-2:
1) Create user status profile as per approval hierarchy with number assignment.
2) Create "Authorization code" for the user status number.
3) Provide "Authorization code" to the SAP user ids as per approval hierarchy.
or
If you have only one app rover, provide authorization of creating order to one user and "Releasing" the order to other user.
Regards,
pardhu

Release strategy(urgent)

hi,
i have doubt regarding PO creation.
Purchase Order has to be approved after modidfication, but,
release strategy is not getting updated when i am modifying my PO......so i can't approve it..........
and i am chaning quantity,delivery date, price and condition type, actually i want to know wht is the problem......... and why this is happening......
and "on wht factors will the release startegy depend ?????????"

Hi,
Please can you clarify the following.
You are saying that it should be approved ONLY after modifying it.
But was it caught by the release strategy BEFORE it was modified?
Or are you saying that when a released PO is modified you want the strategy to be reapplied?
Steve B

Error in Release strategy

Hi,
If I assign the following in a Class, the release strategy is trigger in the PRS with out any enty of the given objects in the Class.
Purchase Requisitioner
Plant
Value
Pl help me out

Hi
Check on it:-
http://www.sap-basis-abap.com/sapmo017.htm
http://www.sap.com/services/pdf/BWP_WP_Release_Strategy.pdf
http://sapdocs.info/wp-content/uploads/2009/07/PR-Release-Strategy-Guide-a-case-study-Free.pdf
http://www.google.co.in/url?sa=t&source=web&cd=13&ved=0CB8QFjACOAo&url=http%3A%2F%2Fwww.sdm-c.com%2Ffiles%2FBarcelona_Mazliach_Automate_Your_Purchasing.ppt&rct=j&q=sap-Release+strategy&ei=6IAYTJ2DHJi80gTx7JS_Cw&usg=AFQjCNGi6UQkRdPdIeVmt7mqSiwZr04-Sw&sig2=rJsnJKRW-_8CQebhDq66Tw
pherasath

Affect on release strategy by ME22N

Dear All,
I want to know that in which scenarios, ME22N will affect the release startegy in a relaesed PO or under release PO like any change in PO or some standard scenarios.
Thanks with regards,
Ankit Gupta

Hi,
Release startegy :
In the standard system, Release strategy will trigger changes in PO are done in to the quantity,unit of measure, or price .
This is controlled by Changeability indicator in release strategy.By this you can determine that release procedure will restarted if purchase order changed & value of item is increased by certain percentage or any change in the value.
Thanks,
AMIT

Standard SAP Report - Payments blocked and released

Hi Experts,
We are having a requirement where the payment will be blocked for the invoices generated through Invoicing Plan.
But we need a report " To know the status of payments blocked and released according to the invoicing plan". Do we have any standard SAP report on this requirement?
By
Prabhu

Hi,
Use t.code: FBL1N , enter company code & select document type "KZ" in dynamic selection
and then select & execute for....
1.Open Items in status segment for not paid to vendor
2.Cleared Items in status segment for paid to vendor
Regards,
Biju K

Call a standard po release or cancel po release in program

Dear all,
How can I call a standard po release (me28) or cancel po release in program
to release or cancel release a po?
Thanks you
John

You need to get the report and when you double click on field ,then it goes to ME28 Transaction.
need to use set parameter id ,
see the below example and which i did in ALV ,it will call MM02 transaction.
REPORT Z_GET_REFRESH no standard page heading.
type-pools : slis.
tables : makt,
         mara.
data : i_fieldcat type slis_t_fieldcat_alv.
CONSTANTS :
gc_refresh TYPE syucomm VALUE '&REFRESH'.
data : begin of i_makt occurs 0,
       matnr like makt-matnr,
       maktx like makt-maktx,
       end of i_makt.
data : v_repid like sy-repid,
       g_user_command type slis_formname value 'USER_COMMAND',
       g_status_set   type slis_formname value 'SET_PF_STATUS',
        lt_event_exit TYPE slis_t_event_exit,
        ls_event_exit TYPE slis_event_exit.
DATA:LC_GLAY TYPE LVC_S_GLAY.
select-options s_matnr for mara-matnr .
start-of-selection.
select matnr maktx from makt into table i_makt
                              where matnr in s_matnr.
end-of-selection.
Fill the fieldcatlog
perform fill_field.
Call the FM
perform call_fm.
*&      Form fill_field
      text
--> p1        text
<-- p2        text
FORM fill_field.
data wa_fieldcat type slis_fieldcat_alv.
clear : wa_fieldcat.
wa_fieldcat-tabname = 'I_MAKT'.
wa_fieldcat-fieldname = 'MATNR'.
wa_fieldcat-outputlen = '18'.
wa_fieldcat-seltext_l = 'Material #'.
wa_fieldcat-col_pos = '1'.
append wa_fieldcat to i_fieldcat.
clear : wa_fieldcat.
wa_fieldcat-tabname = 'I_MAKT'.
wa_fieldcat-fieldname = 'MAKTX'.
wa_fieldcat-outputlen = '40'.
wa_fieldcat-seltext_l = 'Material Desc'.
wa_fieldcat-col_pos = '2'.
append wa_fieldcat to i_fieldcat.
ENDFORM.                    " fill_field
*&      Form call_fm
      text
--> p1        text
<-- p2        text
FORM call_fm.
v_repid = sy-repid.
LC_GLAY-EDT_CLL_CB = 'X'.
CLEAR ls_event_exit.
ls_event_exit-ucomm = gc_refresh.    " Refresh
ls_event_exit-after = 'X'.
APPEND ls_event_exit TO lt_event_exit.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
I_INTERFACE_CHECK                 = ' '
I_BYPASSING_BUFFER                =
I_BUFFER_ACTIVE                   = ' '
      I_CALLBACK_PROGRAM                = v_repid
      I_CALLBACK_PF_STATUS_SET          = g_status_set
      I_CALLBACK_USER_COMMAND           = g_user_command
I_CALLBACK_TOP_OF_PAGE            = ' '
I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
I_CALLBACK_HTML_END_OF_LIST       = ' '
I_STRUCTURE_NAME                  =
I_BACKGROUND_ID                   = ' '
I_GRID_TITLE                      =
    I_GRID_SETTINGS                   = LC_GLAY
IS_LAYOUT                         =
      IT_FIELDCAT                       = i_fieldcat
IT_EXCLUDING                      =
IT_SPECIAL_GROUPS                 =
IT_SORT                           =
IT_FILTER                         =
IS_SEL_HIDE                       =
I_DEFAULT                         = 'X'
I_SAVE                            = ' '
IS_VARIANT                        =
IT_EVENTS                         =
   IT_EVENT_EXIT                     = lt_event_exit
IS_PRINT                          =
IS_REPREP_ID                      =
I_SCREEN_START_COLUMN             = 0
I_SCREEN_START_LINE               = 0
I_SCREEN_END_COLUMN               = 0
I_SCREEN_END_LINE                 = 0
IT_ALV_GRAPHICS                   =
IT_ADD_FIELDCAT                   =
IT_HYPERLINK                      =
I_HTML_HEIGHT_TOP                 =
I_HTML_HEIGHT_END                 =
IT_EXCEPT_QINFO                   =
IMPORTING
E_EXIT_CAUSED_BY_CALLER           =
ES_EXIT_CAUSED_BY_USER            =
    TABLES
      T_OUTTAB                          = i_makt
   EXCEPTIONS
     PROGRAM_ERROR                     = 1
     OTHERS                            = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " call_fm
      FORM USER_COMMAND                                             *
FORM user_command USING r_ucomm LIKE sy-ucomm
            rs_selfield TYPE slis_selfield.                 "#EC CALLED
data i_RSPARAMS like RSPARAMS occurs 0.
CASE R_UCOMM.
    WHEN '&IC1'.
      read table i_makt index rs_selfield-tabindex.
     <b> SET PARAMETER ID 'MAT' FIELD i_makt-matnr.
      if not i_makt-matnr is initial.
        call transaction 'MM02' and skip first screen.
      endif.</b>
    when '&REFRESH'.
      CALL FUNCTION 'RS_REFRESH_FROM_SELECTOPTIONS'
        EXPORTING
          CURR_REPORT           = v_repid
IMPORTING
SP                    =
        TABLES
         SELECTION_TABLE       = i_RSPARAMS
       EXCEPTIONS
         NOT_FOUND             = 1
         NO_REPORT             = 2
         OTHERS                = 3
      IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      submit z_get_refresh with selection-table i_RSPARAMS.
      rs_selfield-refresh = 'X'.
ENDCASE.
MOVE '&REFRESH' TO r_ucomm.
ENDFORM.
      FORM set_pf_status                                            *
FORM SET_PF_STATUS USING rt_extab TYPE slis_t_extab.
DELETE Rt_extab WHERE fcode = gc_refresh.
SET PF-STATUS 'STANDARD_FULLSCREEN' OF PROGRAM 'SAPLKKBL'
      EXCLUDING Rt_extab.
*SET PF-STATUS 'STANDARD' EXCLUDING rt_extab.
SET TITLEBAR sy-tcode.
ENDFORM.
Thanks
Seshu

Release? while assigning Z Message Type to a Standard SAP IDOC Basic type

Hi Experts,
Am trying to assign a custom Message Type to a Standard SAP IDOC Basic type in WE82 transaction, but am not sure How to find the Release(last column of WE82 Tx)? Pls. let me know.
Thank you

Hello,
In case of IDOC, Go to Transaction WE30, type your IDOC name & select basic type & extension.
After that select Go to -> Header data (Shift+F7), you will Idoc header info. In the same pop-up you will find IDOC release for which version.
Regards,
Sameer

Standard sap BACK, CANCEL icons affected by custom status - why?

Hello SDN Community,
I was trying to clean up some items in the Function List display of my custom status and I had deleted a couple of items that I had created incorrectly.
After that, I ran my transaction and clicked the standard sap EXIT icon. It returned me to the initial SAP screen. However, I noticed that the BACK and CANCEL icons were greyed out. It was working fine 5 minutes before this.
Would anyone know what I might have done to cause this to happen? Things to look for, places to check?
Thank you,
Dean Atteberry.

Rich,
Both buttons (BACK, CANCEL) have function codes of the same name.
The EXIT button has function code of "EXIT".
All three are active as long as my transaction is running and they function fine from any screen (about 6 screens).
However, when I hit any one of the three (BACK, EXIT, CANCEL), it returns me to the SAP Easy Access screen. On that screen BACK and CANCEL are greyed out. EXIT is active.
When I hit back from my first screen, my program does "LEAVE PROGRAM". So I turned on debugger and put SY-PFKEY in the variable display and hit BACK. It went directly to Easy Access, so I didn't see anything. However, when I typed in SE38 in command line, it was still in debugging mode and "SESSION" showed up in debug variable display for SY-PFKEY.
Program for easy access is SAPLSMTR_NAVIGATION and when I looked in SE41 for status SESSION, found it. I can see function code settings, but not sure what it means.
Looks like I managed to mess something up internally when I deleted those incorrect function codes because my program works fine. Its when I return to SAP that this happens.
Also tried logging off and logging on in hopes that it was transient, but still happening. 8-(
Thank you for your help.
Dean Atteberry.

How release of PR is affected in standard SAP

Dear experts,
Please help. How standard SAP PR release is affected. I want that if any change in PR , release will be affected. How this can be done. Please advise
Thank you
Kind regards,
Zusen

>
Badruddoza Zusen wrote:
> Hi
>
> Thank you for your reply.
>
> I checked that re-trigger is happened if i change value only when value exceed the certain level as specified in the release strategy. But, what i need to do if i want that any change in value will re-trigger release strategy.
>
> Please advise.
>
> Kind regards,
> Zusen
To pick up release strategy for all value your value characteristic should read:
>= 0
Meaning Greater than or = 0, even the release strategy will pick up PO's with 0 value in this case.
Edited by: Afshad Irani on Jun 21, 2010 9:53 AM

Re: Cancelling of approval in standard SAP release strategy.

Similar Messages

Maybe you are looking for