Preq release strategy

My Preq release indicator has it's changeability indicator set to 4. So if the value increases (qty or price) after release this works fine and PR is resent for approval
However if I change the material after it's been released (ME52N) but the value does not change the release strategy's not triggerred again. Is there no means of making the release strategy field dependant, or should I set the material field to display only in the field selection after release. My concern is a Preq could be created for say u20AC100, the PO changed and material A replaced by material B for the same value (or less) and the release strategy not triggered.
Thanks in advance.

I think the only way is to set the field selection of the release ID to display fields.
This will restrict the users from changing the field value once the Release ID say "4" is set.

Similar Messages

Preq release strategy tab disappears

We are having an issue where a few odd times, we will find that a Preq is missing its Release Strategy Tab. Here is an example, and my findings so far below the image.
Checking the Workflow, I see there was a workflow started, so I know the release strategy must have kicked in.
I see that the workflow went to error, with the error saying "No Authorization to Release"
However I checked the user, and they do have the correct Release Level Role.
So I'm not sure where to check next?

Our release strategies are just on PR value, see screens below.

Extracting values for characteristic on release strategy of Preq

hello
we have Preq release strategy based on classification and the release is based on amount. in the class, one of the characteristics contains the amount above which the strategy is being triggered: how can I extract all the values for all the strategies from this characteristic? is there a table for it?

Hi,
Please check the AUSP table for release strtegies and CAWN table for characteristics. Please check below link for additional information. Thanking you.
Release strategy tables

New release strategy / Old PReqs

Hi,
New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
Many thanks in advance for your clues.
Regards,
Grzegorz

Hi,
Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

Release strategy for PREQs created from PM work order

Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
Desislava

Hi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj

Release Strategy for Preq

Hi SAPgurus...
I have release strategy implemented in my system with 7 level approvals for the Pur. Req . Now i need to Change the release strategy to 4 levels approval based on one of the Characterstics that is the Preq Net Price. Which cud be the best process to ahcieve it , since if i am going to keep the old one and create a new one then wheneve similar characterstics appear the system cant recognize which strategy to apply.......
Please can any one advice me how can i approach ...
Regards
Balaji

Hi Lakshman, Srini & Venki
From ur statements i understand to modify the existing ones , okie as u said i will delete the extra release codes and modify it . Now fine..
What happens when i moved to prodcution these changes then, say if i have Preq
with older version of release strategy how it impacts.....How i can handle this in
effective manner...To my knowledge i think whenever if i go for a change in preq the new release strategy will be affected....( In this case its fine) what abt the ones which doesnt need a change and has to be released....
Thanks for the time ...
Regards
Balaji

Challenge for release strategy in Preq

hi all.
our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
their release is based on several factors:
1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
2) amount 2001>6250 it must be released by the following:
WC1and/or Maintenance manager
or
WC2 and/or maintenace manager
or
WC3 and/or maintenance manager.
the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases first the Preq is released and there is no further need to release by WCn.
anything >6250 must be released by the maintenance manager.
our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2: how can i set the strategy in such a way that it can perform the release and/or?
can someone help?

Hi Alisa,
Your Requirement is very Complex,
first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
for that you need to have different Release codes assigned to the user in the roles.
for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
Please revert back.
Regards,
Yawar Khan

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

User Exit for Purchase Order Release Strategy

Hi,
I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
Thanks in advance.
Mick

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points if useful
Rgds,
Naren

Class and release group and code in release strategy??

hi experts ,
Can some body explain me..
I have created Characteristics and Class for for release strategy.
But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
I m using the same class what i have created for my company..
So how to over come this issue
Thanks

Release Prerequisites
Definition
The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
Release Indicator
Definition
When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
What does the release indicator determine?
Requisitions...
External purchasing documents....
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether an RFQ or a PO may be created with reference to the item
Whether the document may be changed by Purchasing after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether the purchasing document is released for transmission
Alternative Release
Definition
Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
Release w. Classification (PReqs./Ext. Pur. Docs.)
Use
The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
Operation of Release Procedure w. Classification
The characteristic values from a requisition or external purchasing document are passed on to the classification system.
The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
The persons responsible for the release codes process the document in the sequence defined in the release strategy.

Purchase requsitions into table EPRTRANS when using release strategy

Hi,
We are working with release strategy.
It is not passible to insert purchase requsitions into the table EPRTRANS when I choose e.g.a material group which
has been declared as a relevant criteria for release strategy. How can this problem be achived ?
Regards
Alexander
Edited by: AlexanderZiegler on Sep 23, 2009 11:25 AM

pls. comment out this perform
     PERFORM bbp_release_check USING l_xeban
                                     l_yeban
                            CHANGING no_update
                                     now_released.
     IF no_update = 'X'.                   " preq not yet released
       CONTINUE.
     ENDIF.

Release Strategy and workflow in Purchase Requisition

Hello All,
My client wants to activate the release strategy and workflow at the purch req and PO levels. They allow users to create a Preq and reference that preq to the PO, or users may create a PO without referencing a Preq. Since they have the release strategy and workflow working on both levels, what they want done is, if a PO has a Preq reference, it does not need to go through another approval process on the PO level as it has already been approved on the Preq level. Therefore if a Preq is reference in a PO, the PO workflow and release strategy should not be taken into account. Can this happen as a standard config, or will this need a "user exit"?
Thanks in advance for your help!!

You will need to activate the user exit. This will keep the PO release strategy simple.
Have a flag (use USRC1 or USRN1). In your PO release strategy classification, maintain only X in this characteristic.
In the user exit, check whether the PO is created with reference to PR. If yes, pass "blank" to USRC1, else pass "X". The release will be triggered only in case of X.
Just a couple of points:
1) What will you do if one item in PO is created with reference to PR and the another item is not?
2) What will you do if one item is partially referenced to PR (i.e PR quantity is 100, PO quantity is 200 - of which 100 is referenced to PR and other 100 is not - this is possible by changing in delivery schedule)?
Hope this helps
Lakshman

Release strategy challenge

hi all.
our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
their release is based on several factors:
1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
2) amount 2001>6250 it must be released by the following:
WC1and/or Maintenance manager
or
WC2 and/or maintenace manager
or
WC3 and/or maintenance manager.
the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases, the Preq is released.
anything >6250 must be released by the maintenance manager.
our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2.
can someone help?

Hi Alisa,
Your Requirement is very Complex,
first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
for that you need to have different Release codes assigned to the user in the roles.
for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
Please revert back.
Regards,
Yawar Khan

Release Strategy in PO for direct materials not driven by MRP

We have a requirement to enable release strategy for purchase orders created for direct materials that are not driven from an MRP requirement for a single plant.
Request you to let me know how I can make this work.
I have an option to make it mandatory to have Preq for these PO's and can enable release strategy for Preq which are created other than MRP.
request to let me know if there are other options in PO's itself where I can find that the Purchase orders are created directly and put release strategy in it.
Thanks and Regards
Murali

Hi Murali,
Standard SAP provides PO release strategy at header level only and not at item level.
So you can create a new PO document type and allow use of only this document type for manual PO creation.
Then set-up PO release strategy for newly created document type, where one of the primary characteristic will be Order Type (Purchasing).
Hope this will fulfill your requirements.
-Ravi

Release strategy: problems after changing the price

HI Experts,
I have the follwing problem.
I´ve setup the release strategy for Purchase reqs.
The strategy includes 3 approval levels.
release indicator with changeability 4 and a value of 0,1% for the first two approval levels.
I´m able to release it, but if I release the first two appoval levels and change the Preq the release strategy goes back to the first level. Fine.
But the problem is now that I´m able to release the first level but if I try to release the second one I get a error message.
I guess the problem is the changeability - but how can I solve this issue?
The system have the cancel all approvals if someone changes the price.
Any ideas?
Thanks
Alex

HI RJ,
the exact message is "Release prerequisite not fulfilled".
The system should act in the following way:
Approval levels:
1. Supervisor
2. Manager
3. General Manager
1 and 2 is approved.
Then the requisitioner changes the price.
Release will be changeled (Releases already effected will be cancelled).
OK that work, now the release process starts with level 1.
1. Approved --> OK
2- try to approve and get the message "Release prerequisite not fulfilled".
1 and 2 have the same release indicator with 4 and 0,1%.
Thanks
Alex

Preq release strategy

Similar Messages

Maybe you are looking for