List of open PO in release strategy

Hello Experts,
Where can we check the list of service PO's which are still in the release strategy.
can you please give the the table and field for it.
regards and thanks,
YK

Hi Kumar,
thanks for thye prompt reply.
i also wanted to kno at what level they are pending in the release strategy.
in my case we have only 2 levels of approval for PO i.e FI and HOD.
can you please help me further.
regards and thanks
YK

Similar Messages

Release Strategy Question

Hi,
Can anyone explain me with example, why is it that we can have only one class and not more, when configuring groups in the release strategy.
Why is it mandatory to have only one class for overall and one class for line item release, can someone explain with examples.
The system allows creation of multiple groups, but all have to use the same Class when it comes to overall release/ Line item release.
I am not able to understand the reason behind this restriction as of now, can someone share some insights.
Thanks
Shailesh

Hi,
Better & always keep one release class ....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.Under each separate class keep your requires characteristics.Then do necessary confuguration for release statergy.
For more check the links:
/people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues
Re: Class and release group and code in release strategy??
Regards,
Biju K

PR - How to use distinct release strategy

Hello SAP's gurus,
We use the procedure with classification for our release strategies.
I cannot undestrand why I cannot work with 2 disctinct class (it means different characteristics list) for my company.
Rel.Grp   /Rel.obj.   / OvRelPReq    /Class
ZY          /1              /NO                 /RELEASE_STRATEGY_1
ZZ          /1              /NO                  /RELEASE_STRATEGY_2
We would like to define specific characteristics depending on the currency used in the PR.
It means, if currency is USD (table CEBAN/WAERS) : characteristic "Total Value of Item in USD" (table CEBAN/GSWRT, currency USD) should be used and if the currency is EUR : characteristic "Total Value of Item in EUR" (table CEBAN/GSWRT, currency EUR) should be used in the release strategy.
How can I work to set up a list of characteristics for the release strategy different from a currency to another one?
Thank you so much in advance for your help.

I'll have a quick check but assuming GSWRT is purely a value figure, that won't provide the distinction you want. You need to use a characteristic that represents the currency i.e. use CEBAN / WAERS. That will allow you distinguish according to the cirrency.

Change in Purchase Order Release Strategy Values

Dear All,
I am in process of changing Purchase Order release strategy values.
I have following release strategy -
                       Current Value                  (Proposed Value)
Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
My questions are -
1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
2) Will this change affect the existing Purchase Orders (already created) which are released?
3) Are there any risk factors?
Can you pl. put light on above questions?
Regards,
Prashant Kolhatkar

Hi,
Actually, what you had given is not enough to determine if the existing PO will be impacted or not
If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
Hope this help

Release strategy tab is not coming in SES

Hi All,
I am facing a issue where I have created an SES, and release strategy is assigned to this SES. Problem is somehow the user is not able to see the release tab when he go wants to release the SES. The release tab is missing from the SES.
Am sure somebody has faced this kind of issue and have any idea how to correct this.
Thanks

Hi,
The direct reason that there is no release icon available in ML81N
is inconsistency in the field ESSR-FRGRL for affected SES's.
This field should be filled with 'X' as all those SES are subject
for release.
Have you changed customizing for involved release strategy recently ?
If a relase strategy is created with a certain name and documents are
created with respect to it afterwards, this release strategy should be
changed then IF AND ONLY IF a NEW name is assigned to it as well. In
other words, if such a strategy is already use, it should be RENAMED
before applying the desired changes.
Otherwise you will run into the observed inconsistencies when trying to
edit documents which were created BEFORE the strategy was changed
(since the system at some point always checks the NAME of the strategy
to be changed, NOT the content).
So if this case happens only for already created SES a good solution
for it is to delete affected SES and create a new one with changed
release strategy.
I would delete affected SES and create it again.
It seems to be the fastest way to resolve this issue.
If you need a correction for this inconsistency issue, please open a SAP ticket for your problem.
Regards,
Edit

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

Release Strategy to be reset for any change in purchase order

Hi Experts,
At present the release strategy configured is for any change in the value of the purchase order, the release strategy is reset. Now the the client wants that for even any text change of a word, text, quantity, value, addition, deletion the release strategy should be reset.
Can any one guide to configure the release strategy for any change. Also please provide the list of standard parameters/scenario (E.g. change of price, change of quantity etc) for which the release strategy can be configured to be reset.
Thanks in advance.
AJ

Hi Diwakar,
I too have the same problem. I tried with Changeable indicator "1". The system does not allow to make any change to the Purchase Order even after the first level of Release. But the requirement is that the system should Reset the Release Strategy for even minor Change in the PO.
Regards,
S.Raghavan

Purchase requisition release strategy

I want each purchase requisition should be created with valid release strategy. The problem presently is that if somebody puts wrong parametes (such as purchasing group, currency) the purchase requisition will not be applicable to release and the purchase order can be easily created. So in such cases there is no need to release purchase requisition which is not correct for business point.
Pls advise.

Hi Balaji
Ur need is appreciated but inorder for that to work we have to make sure that all the possible combinations exist in ur characteristics list which may not be possible all times.
So better way would be to check whether the characteristics combinations of ur class and the corresponding data of ur requisitions matches and trigger error msg if differs.
Ex: Plant and doc type be the characteristics used in ur class.
Check whether the PR has only the plants and doc types that is specified in ur release strategy and if no trigger error msg.
Try this using BAPI also. Get help from ur ABAPer.
Thx
Raja

Purchase Order E-mailing with Release Strategy

Hello,
We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
Print Programs:
/SMB11/FM06P
/SMB40/FM06P
SAPFM06P (Sapscript Only)
Forms:
/SMB11/BL_MMPO_L
/SMB11/MMPO_L
/SMB40/MMPO_L

Hi,
Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
1. You must maintain an e-mail address in the address in the vendor master.
2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
For more details, check SAP note:191470
Regards,
Biju K

How to apply newly transported release strategy to existing POs ?

Hi,
We transported a new release strategy to production
The new POs created are catching the rel strat B if they meet criteria
But some of the existing POs also meet the criteria for B and they should also take up this new release strategy
We cannot change the POs in ME22N, busines refuses to make any change to POs
How can we apply our new rel strategy to these POs ? has the SAP provided any standard function module to report?
thank you
B

thankyou for the replies.
finally we got minor price change done manually in all the POs to get the new rel strategy on them
Open POs , no change done - Did not pick release strategy (then it was no problem at the first place)
Open POs , change done in price - picked the new release strategy
Open POs , no change done but click on 'check' button in change mode - Could not test this one bcoz all POs are now converted. But I put break point in save user exit (which also plays part in determining the new release strategy) it did not stop at the break point and I gave message 'No data changed' so I think this action will not redetermine release strategy. It was very useful if it did though.
thank you.

How to determine the right PR Release strategy

Hi Experts,
Could u help me to solve this problem!
As our business, we want the system automatically determine the right Release Strategy based on the total Amount(amt) of PR such as
- if PR total amt <= 1000 USD --> must checked by only Department Manager (DM)
- if PR total amt >1000 USD --> must checked by Department Manager (DM) and General Director (GD)
so i've already configured system like that:
1. Create characteristic : CEBAN_GSWRT (Structure CEBAN ; Field GSWRT)
2. create anew Class CEBAN_GSWRT, which associated with above Characteristic
3. Create release Group "03", which associated with above Class (CEBAN_GSWRT) and cheked "Overall Release PR"
4. Create Release Code DM ; GD
5. Create two Release Strategy such as:
5.1. Strategy 01 - DM Only, which have only DM release code & assigned to class CEBAN_GSWRT and the value identified here is <=1000 USD
5.2 Strategy 02 - DM -GD , which have DM & GD release code & assigned to class CEBAN_GSWRT and the value identified here is >1000 USD
then, i created two PRs, one have amt <1000 USD , another >1000 USD, but the system alway get the same Release Strategy 01,its mean that system allway apply the first case Amt of PR <1000 USD.
Note: In the Document Type i checked Overall Release also!
So, pls help me to show out wrong or missing steps!
Thanks in advance
Vietttq.
Edited by: viettq on Sep 1, 2009 4:32 AM

Hi,
Please open the below link, it will help you to understand the complete step by step process:
http://www.sap123.com/showthread.php?t=59

PR/PO Release Strategy

Hi All,
Actually there is a requirement where i need for options in PR/PO release strategy.
The four options that i need are
>Approve
>Cancel
>Recommend to approve
>Recommend to reject
The SAP provided standard options are approve and cancel.
How can i add the two other options in the standard workflow?
pls let me know.
Thanks n Regards,
Raj

The standard workflow does not have any user decision step having two buttons approve and reject
but it directly opens up ME29N.
so first you wil have to remove this dialog step from the workflow which opens ME29N
then keep your decision step with four buttons and handle the outcomes

Message no. CZ160 - Select a valid release strategy - IS Retail

while assigning PR release strategy to site thru' "Determination of Release Strategy" under tcode WB02, i am getting following error message.
Select a valid release strategy
Message no. CZ160
Diagnosis
The release strategy 01 is not defined.
Procedure
List the permissible values using F4, and choose a valid release strategy.
FYI, i configured PR release strategy "01" with required config. requirements and checcked the same thru' simulation and it is working fine.

Hi,
Please follow the steps;
1. Create characteristics via tcode CT04
2. Create Class for class type 032. Via tcode CL02
3. Then go to SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure. create release group, rel obj, class 032.
Next, set up release codes followed by release indicator.
Then the release strategies.
4. go to tcode CL20N to assign the release group and release strategy to the class and class type.
5. SPRO -> MM -> Pur -> PR -> Release Procedure with Classification -> Set up procedure -> Check Release Strategies

Release strategy tables

Please tell me the tables used for release strategy of PR, PO, service PR, sercice PO, RFQ, contract, and delivery schedules.
Is there a method of finding out the table by some methodology. It is not possible to remember all the tables.
In case of PR item level release is required. Give some guidelines as to how to activate item level guidlines. it is possible both with and without classification.
Regards

HI,
Release strategy tables
Release strategy without classification
T161I as described above.
T161E Release code and Description
T161S Release indicator
T161G Assignment to release indicator
T161F Prerequisites
Release strategy with classification
T16FG, T16FS as described above.
T16FH description of the release group
T16FT description of the release strategy
T16FC Release code
T16FD Description of the release code
T16FV Prerequisites and actions
T16FK Assignment to release indicator
T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator
Other tables are
EKBE History per Purchasing Document
EKBZ History per Purchasing Document: Delivery Costs
EKKN Account Assignment in Purchasing Document
EKPA Partner Roles in Purchasing
EKPB "Material Provided" Item in Purchasing Document
EKPV Shipping Data For Stock Transfer of Purchasing Document Item
EKRS ERS Procedure: Goods (Merchandise) Movements to be Invoiced
EKUB Index for Stock Transport Orders for Material
EBAN table has fields for release status and indicator.
To See the tables
goto Transaction SE11, in the field Table click F4, Click on Information system
In the applciation Compnnets enter the following & execute
MM* Materials Management
MM-CBP* Consumption-Based Planning
MM-PUR* Purchasing
MM-SRV* External Services
MM-IM* Inventory Management
MM-IV* Invoice Verification
MM-IS* Information System
MM-EDI* Electronic Data Inter
MM-FT* Foreign trade
OR
goto SE16 Click F4, You have two options Information system & Sap Applications.
Click on SAP Applications & selec the application you wnat to see, for E.g Purchasing you can click on materials managemnt, Purchasing if you drill down you will see the list of tables....
http://help.sap.com/saphelp_47x200/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Check release stratergy with and w/o classification
Thanks & Regards,
Kiran

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.

List of open PO in release strategy

Similar Messages

Maybe you are looking for