Purchase Requistion release procedure

Hi,
Purchase requistion header level approval procedure activated. We required two level of approvals procedure based on total PR value range. Eventhrough i have maintained relase strategy its pulls always single stragey.
Do the needful.
Regards
Mohan

Dear,
Have a look at:
http://www.scribd.com/doc/548510/SAP-Release-Strategy
Regards,
Syed Hussain.

Similar Messages

Purchase Order release procedure

Hi All,
My client is having following requirement for Purchase Order release procedure.
Plant 1                    -    1 Release code (Manager)
Plant 2             -    2 Release Codes (Manager, Sr Manager)
Plant 3             -    3 Release Codes (Purchase Officer, Manager, Sr Manager)
All plants are assigned to one company code. Please advise me how I can map above requirement in sap.
Thanks & Regards,
Nagi

Hi Nagi,
In PO Realease startegy configuration, you need to decide and select the Release objects for which the system should trigger release for the document. you should work with Characteristics for each object (Your requirement is for 3plants) so in one of your characteristic WERKS should be your field along with other characteristics based on your requirements such as Total Net Value, Doc type etc.
Create Characteristics in CT04 for the class type 032 and proceed maintaining the release Group and Release codes as per your requirement.
Refer the following thread and revert if any confusions...
http://**********************/2008/11/release-procedure-release-strategy-main.html
Regards
Shiva

Release code - Purchase requisition - Release Procedure

Hello,
In the purchase requisition release procedure with classification, we are defining release codes say K, P etc.
My doubt is , Is this being defined else where based upon the designatin of the person in the organisation, or else, we are defining here straight away?
Best regards,
K.Kumaran.

HI
You are correct, you need to define the release code there only. There is no other place where it is defined. What you have to ensure is make sure that it is of Two character and not single. Assign the codes against the designation of the person as per your requirement.
Regards

TWO CURRENCIES IN ONE Purchase Orders Release Procedure.

TWO CURRENCIES IN ONE Purchase Orders Release Procedure.
Please provide a solution if a release strategy is maintained for two currencies like USD and SGD for more clarification please Read the below Requirement.
Requirement for Singapore:
u2022          COMPANY Asia (Singapore) wants its own Purchase order release strategy is based on their local currency (SGD)
u2022          Whereas COMPANY is using only USD as currency in Purchase order release strategy.
u2022          Standard SAP works based on Character currency which is defining in Class of Purchase release strategy and converts with Local currency to compare with Character Currency.
Required analysis:
u2022          The value assigned in classification is based on Conversion from SGD to USD, Due to Exchange rate fluctuations the assigned value is differ by large amounts and hence system is either determining the higher release strategy or Lower release strategy
u2022          But during Release Strategy Configuration the Net order Value is assigned as 3600 USD considering the Exchange as 1.388889.
u2022          As per the exchange rate in the purchase order 1.3799 the system is calculation the PO Net order Value but the Strategy is Determined based on the value maintained according to exchange Rate 1.388889
In the Purchase Order the system is
Ex: Total Purchase Order Value is 4765.21 SGD and 3453.30 in USD
      For Level 1 the value limit is 5000 SGD if it exceeds 5000 SGD it has to go to his manager (Level 2) Exchange rate on 01.04.2008 is 1.3799.
System Considerations:
Possible Solution:
1.        Create a new Class with Characteristic with Currency Value SGD System should determine the class based on the combination of Plant 6000 and Document Category F Purchase Order.
2.        By using Enhancement spot with Function Module ME_RELEASE_STRATEGIE/ ME_RELEASE_STRATEGIE_EKKO
Logic:
1.        System will determine the class PUR_RELEASE from table T16FG if the system finds Plant as 6000 and Document Category as F Then replace PUR_RELEASE with New class as ZPUR _6000.
2.        Maintain Z table for the combination of Plant and Class for future requirement
Edited by: Mohammad Irfan on Jun 8, 2009 10:41 AM

Hi Mohamed,
You can create separate characteristics far all check points and assign those to class.
Regards,
Prasath

Purchase Requisition Release Procedure Modification

Hi
In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
Appreciate any guidance on these issues
Thanks
Sriram

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

Purchase requisition release procedure through User-Exit

Hi Workflow Guru,
I have a requirement to configure purchase requisition workflow . the workflow should trigger through release strategy.
The approver should determine through user-exit and the approver should determine based on value and quantity and that can be define in user-exit. as per my knowledge the value should mantain in SPRO-Release procedure. Please clarify me is it possible through user-exit. I am worked on user-exit for release procedure based on purchasing group.
Thanks in advance.
Regards,
Ranjan Tiwari

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

Purchase Requistion Release Stratergy

Hi,
I have a situation where I need to get the details of the classification Net total in purchase Requistion for the particluar Release Stratergy and Release Group from the relevant table for raising an event manually in work flow, which I am uable to trace out.Please help in this regard for identifying the tables which holds the data of the Net value for the same.
Thanks in Advance for your Help
Regards,
Krishna Mukthineni

Hi Krishna,
the classifications of the release strategy is best read via the API (interfaces) for the class system. To get quick results and to check, if your designed process could be working at all, you could hard-code the class' name and it's characteristics. Later on -- to be more precisely -- you should read the class name from the customizing and the characteristic definition from the class system.
To get an example of how SAP determines the release strategy from the classification (which is kinda the other way round), you may consult the following function modules/coding sections:
Function module ME_REL_COM_STRATEGY_EBAN
--> Form strategie_neu
->-> Function module CLSC_SELECT_OBJECTS
To see the usage of this function module within your system, you could set a break-point there and create/change a requisition in your system.
The internal table iausp holds the values of the characteristics.
The referenced characteristic you'll be possibly looking for is based on CEKKO-GNETW
Best regards,
Florin

Purchase Requistion Release Stategy not tiggering

Purchase requision i have acivated 3 levels.
i have used 3 characteristic like plant, doc type and value.
1.<=30L
2.>30 - 75 L
3. > 75L
first two level system s tiggering well. above 75 L system not triggering the release strategy. Its showoing Release starategy Inconsistent.. only 75L to 1 Crore not triggeing. above one crose system triggering the 3 level which > 75 L.
Pls tell me how to rectify this error.

Hi,
sometimes it helps to set finite ranges. In your example the last range would 75-9999 (or seomething like this).
But check if you really fulfil the criteria to reach this level.
regards, Paul.

Purchase Requistion release date as system date

Dear Experts,
Our Requirement is the top management want to know time taken to release a purchase requisition,means the duration
between purchase requisition creation date to release date.
here user are manually changing the release date to system date to know duration exact time duration between the creation date and release date,so user requirement is the release date should be system date so he can easily understand when the requisition is released.
we are thinking that,if we make the release date as system date,please suggest me.
Thanks in Advance.
Varun

Dear Madhu,
1.)     Whenever you are creating a new PR system will automatically take that PR creation date as system date.
2.)     All the releases in SAP System will be recorded as Item/Header change and system will maintain their history in Item/Header change details
3.)     If your requirement is to track the duration between creation, release of levels it can be very much possible by creating a quary it self.
Regardsu2026
Srini Rao

Purchase Requistion Release Strategy

Hi All,
I have created new release code.
but it not working.
In the log i could see workflow error. Error is "Role resolution for code R4, group 02, effected via customer exit"
could you please tell me what i am missing.
Thanks,
raju

Hi Raju,
In the documentation of Set Up Procedure with Classification
Release codes
Here you create the release codes that you need for your release
strategy and assign the codes to your release group. If a release code
is to be used in workflow, indicate this accordingly in the Workflow
field.
The Workflow indicator is also used to control role resolution:
"1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system.
To do so, you must assign the release point in the section Workflow (see
below).
"9 - Role Resolution via User Exit" <<<<<<<<<<<<<<<<<<<<<<
Here you use customer exit M06B0001 to define a role resolution of your
own.
I guess you have defined a "9". In this case the user exit should be used or the workflow indicator should be changed to "1".
Best Regards,
Arminda Jack

Purchase Requistion Release Reset by ME54n & ME54

Dear all
Once PR is created, then Released by ME54n or ME54, then RFQ is processed wrt PR, then after if user want to reset release by ME54, the system prompts error message and not allowed reset release. BUt if user use T-code ME54n, the system allows to reset release.
we need, the system should not also allow to reset release for T-code ME54n.
Please suggest solution
Thanks
RS

Dear Vivek,
I raised this to SAP and got reply from SAP.
===========================================================================
ME54N allows the user to unrelease a purchase requisition linked to a
purchase order or a request for quotation. Please see following
attached note 686022 which explains this behavior.
Symptom
You create a purchase order (or a request for quotation) with reference
to a released purchase requisition.
If you use ME54N to unrelease the purchase requisition, the error
message ME110 (or ME109) is not processed.
Reason and Prerequisites
ME54N allows the user to unrelease a purchase requisition linked to a
purchase order or a request for quotation. This is correct behaviour andconstitutes a new design.
The following modification keeps the old functionality (ME54) available.You have to customize message ME110 (or ME109) as an error message.
After pressing the cancel release button, the system will process an
information message (ME110 or ME109) and the release will not be
cancelled.
If you want to use the old functionality in ME54, you can implement the
modification as note 686022.
Hope this informatoin will be helpful.
===========================================================================
Can you suggest, the error settings is already there and its trigger only for ME54, and not for ME54n
AS per the reply from SAP, can advice me on this
As per your previous reply, i got basis team and authorization team, to whom i need to ask to set M_EINK_FRG for ME54n?
Thanks
RS
Edited by: Ramapuram Saravanan on Feb 16, 2009 6:05 AM
Edited by: Ramapuram Saravanan on Feb 16, 2009 6:06 AM

Purchase Requistion Release Strategy Codes

Hello,
Do we have any solution where we can increase the number of PR release codes from sap standard 8 to say 10. Is there a user exit or function module to do that. let me know.
Regards
Bala

There is nothing availble for this kind of issue.

Purchase Requistion Release **IMP**

Hello Experts,
I have posted a thread before with same issue it was answered by lakhsmi but i really need your advise can we control release strategies through user ids (i mean SAP User ID) Is this a good practice for an instance
User A can release any Preq upto x$
User B can release any Preq upto xx$
User C can release any PReq upto xxx$
Please if you can provide details in detail
Thank You
Justin

Hi,
We have the most complex release strategy setup in one of our clients' project ( in my entire experience, i can say this is the most complex one). In this, exactly the same I have recently designed a solution as you are looking for....
However, it can not be addressed in standard SAP. It requires User Exit usage.
In PO, of course, countless number of solutions can be developed in user exit (fortunately!!!).
How it works:
We have a ztable that provides the approval routes. For example, for a plant and porg combination, we maintain all possible Approvers' list ( Literally User Names). This approval route is one of the characteristics that determines release strategy. I designed multiple release strategies for all possible approvers for their limit values in $s. From the user exit, PO triggers a pop-up with allowed approvers for the plant and porg combination. User got to select one (else, we triggered error message) based on the selected Approver (approval route), it looks for release strategy applicable. Everything works fine...No issues about maintenance, if you create a z-transaction or z-table maintainable via SM30 in Prod system with limited access restricted to only COA maintenance person.
Regards

BDC/LSMW for SPRO to MM to Purchasing to PR to Release Procedure to ...

Hi experts,
May I know those screen in SPRO can do BDC or LSMW? I am facing problem on trying up the BDC using SM35 on the following screen. (I can't get the transaction code).
The path is:
SPRO -> MM -> Purchasing -> PR -> Release Procedure -> Set up Procedure With Classification -> Release Strategies.. The SAP program is SAPL0ME2, but I can't execute it using SE38 since it's a program Type 'F'.
So may I know any possible way for us to use recording approach on these to do Mass insertion of data?
Thanks.
Cheers,
Wong
Edited by: Julius Bussche on Sep 12, 2008 10:37 AM

Hi Vijay,
First, you can try on SM30, V_T16FS. Simply double-click on 1 release strategy, then Click on "Classification". You will see the classification screen allow us to enter value on each characteristic of the class.
However, I try using SHDB (recording), it shows empty screen on the value for class in the 'Classification' screen.
Thanks.
Cheers,
Isaac.

Release Procedure for every Purchasing documents

Hi,
for a procument of material eg:- Material007
Can I set Release Procedure for Purchase rquisition
then after releasing Purchase rquisition i need to create a RFQ
which is also subject to Release Procedure ,After releasing RFQ I should able to enter into a Contract,which also subject to Release Procedure ,After releasing Contract i need to create a Purchase Order which is also subject to Release Procedure,After releasing Purchase Order only I should be able to Receive the goods.
Is it possible to do this way ?Can any one help me?
Thanks

Why you want to put so many locks??????
well if case your required use below steps for all document typew in IMG.
suggestion to download the BBP from below link also
http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm
3.4.24     Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1     Creation of Characteristics
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
Transaction Code     CT04
2.     On the Characteristic screen, make the following entries.
3.     In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name     Description     User action and values     Note
Select Addnl Data tab
Table Name     Table Name     CEKKO
Field Name     Field Name     GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description     Description     Total net order value
Status     Status     Released
Data Type     Data type     Currency format     Selected by system
Number of characters     Number of characters     15
Decimal places     Decimal places     2
Currency     Currency     INR
Interval vals allowed     Interval values allowed     Check this tick box
Multiple Values     Multiple values allowed     Select this radio button
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2     Creation of Class
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
Transaction Code     CL02
2.     On the Class screen, make the following entries:
Field name     Description     User action and values     Note
Class     Class     PORELPROC
Class Type     Class Type     032
Choose Create icon or white paper icon to create new class.
Description     Description     Purchase Order Release Procedure
Status     Status     Released
Choose Char. Tab to input characteristic name.
Characteristic     Characteristic     POVAL     Created in above step
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3     Configuration of Release Procedure
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
Transaction Code     SPRO
2.     On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Rel. Group     Release Group     02
Class     Class Name      PORELPROC     Created in above step
Description     Description     PO Release Procedure
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the entries.
6.     Choose yellow arrow to go back to popup screen.
7.     Choose Release Codes to select.
8.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Grp     Release group     02     Created in above step
Code     Release Code     01
Workflow     Workflow     Leave it blank
Description     Description     Purchase Officer
Grp     Release group     02     Created in above step
Code     Release Code     02
Workflow     Workflow     Leave it blank
Description     Description     Materials Manager
9.     Choose Enter to complete the entries
10.     Choose Save icon or Ctrl + S to save the entries.
11.     Choose yellow arrow to go back to popup screen.
12.     Choose Release indicator to select.
13.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Release ind.     Release Indicator     1
Released     Released     Leave it blank
Chgable     Changeability     4
Value change %     Change of value     10%
Description     Description     Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind.     Release Indicator     2
Released     Released     Select Check box
Changeable     Changeability     6
Description     Description     Purchase Order Released
14.     Choose Enter to complete the entries
15.     Choose Save icon or Ctrl + S to save the entries.
16.     Choose yellow arrow to go back to popup screen.
17.     Choose Release Strategies to select.
18.     Choose New Entries icon and make the following entries:
19.     System will give new screen New Entries: Details of Added Entries
Field name     Description     User action and values     Note
Release Group     Release group     02
Rel. Stategy     Release Strategy     S1
          Capital Items Release
Release Code     Release Code 1     01
Release Code     Release Code 2     02
20.     Choose Enter to complete the entries.
21.     Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22.     Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23.     Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24.     Choose Next Screen icon or choose F8 to continue.
25.     If you want to simulate the release procedure you can choose Release Simulation icon.
26.     Choose Enter to complete the entries.
27.     To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4     Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Cross-Application Components  Classification System  Assignments  Assign Object to Classes
Transaction Code     CL20N
2.     On the Class screen, make the following entries:
Field name     Description          User action and values     Note
Class Type     Class Type          032
Choose Enter to Assign values.
Release group     Release Group          02
Rel. Strategy     Release strategy          S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.

Purchase Requistion release procedure

Similar Messages

Maybe you are looking for