Release strategy on PS module over budget

Dear All,
I want to configure release strategy on PS module over budget and it should be value based upto 4 level.
Kindly tell me object and procedure to config for PS module only.
Is it possible to release on activity based or network based releases strategy??
Regards
Sanjeet Kumar

Hi Sanjeet,
Please refer the following thread
https://scn.sap.com/thread/1745541
Regards,
Amit

Similar Messages

Purchase order release strategy based on over delivery tolerance level

Hi Boss,
I like to set the Purchase order release strategy based on the over delivery tolerance. But when i checking, the over delivery tolerance filed UEBTO is not in the communication structure CEKKO. Can you please help me how should i extend the CEKKO with field UEBTO.
I do not have the ABAP experience, please guide me with coding.
Thank you,
Siva

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

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

Chek budget in PO with release strategy

Hi
When i created a PO with a release strategy and the comand need it, the budget are not checking at the save, only when i release the PO.
Is it possible to check the budget (on a PM order or on WBS element) at the PO save.
Thank's
serge

Normally checks like those happen once the PO is released ( example - output is not allowed etc)...
You may need to add something in the PO release strategy user exit to do the check before release (after save), Look into the below to see if this works.
Name of the Enhancement: - M06E0004
Name of the function module: - EXIT_SAPLEBND_002
Hope this helps

Release Strategy for Credit Note un the QM Module

Good SAP Guru's,
I have a very important question for you:
Is it possible within in the QM module (Transaction QM12) to implement a Release Strategy based on the value of the credit note to be created.
This should work on the same lines as the Purchase Order Release strategy.
Any guide lines and/or assistance will be gratefully appreciated.
Kind regards,
Leslie

Dear Leslie
We had done a similar kind of development in notification, not for credit memo though , but certainly can be incorporated in this case.We had done this for approving Short shipment and devaitions. If there has to be short shipment to be sent to a customer a notification will be trigered to manager and if he approves it will go for higher approval.
Please find my suggestion for this development
1) Make 3 task codes. for eg Task 1 for credit note is for less than u20AC500.00 . Task 2one for more than 501 and Task 3other one for more than 2001.
2) According the need of the credit notes to be created let the user assign the task and release it.
3) For task no 2 and task No3 a workflow triggers to the corresponding roles Sales manager & General Manager. ( please note that notifications are workflow freindly and standard workflows are available for the same)
4) if Manager wants to approve he can make the Task Complete. ( Notification tasks have 4 stages, outstanding, release, complete, Succussful)
5) Based on the status of the task you can make use of the action box in notification for creating the credit memo.
6) The credit memo creation will have to be developed. You will have to get ABAP support for this. They can either do it through user exit, or call transaction , and incorporate the same in the Action box of notification. (QQMA0001: User Subscreen for Notification Header, QQMA0014 Checks before saving notification )
please let me know your apprehensions
Regards
gajesh

FM Budget Update when reducing Purchase Orders versus Release Strategy

Hi,
We noticed that whenever we reduce the amount of a Purchase Order, the budget is immediately returned to the budget independently of its release status. The budget should only be returned once the changes have been accepted (i.e. at the end of the release strategy).
How can this be achieved? Do I need to make changes to the customisation or are there Badi's and/or user-exits that can be used to change the behaviour?
Many thanks in advance.
Regards,
Guy

Hello Guy,
The budget keeps beeing consumed even though the purchase requisition has been rejected.
The commitment item will only be reduced if you set the deletion indicator.
This means that the budget is not returned just by rejecting the purchase requisition.
Regarding the point that the budget was consumed even if the po was not released, I kindly ask you to check the following information:
According to note 597854, the SAP internal BAdI 'ME_COMMTMNT_PO_RELEV' is defined in a manner allowing you to decide whether the order updates the commitments of the purchase order or not, corresponding to the header data of the purchase order.
The following exceptions are valid in this case:
o Purchase orders that already have a purchase order history or
o Purchase orders, that were actively saved (not held) and already
released, or are not subject to release,
I suggest you to check the BAdIs 'ME_COMMTMNT_PO_RELEV' and 'ME_COMMTMNT_PO_REL_C' and their documentation.
Also, please review attached note 942582 - BAdI ME_COMMTMNT_PO_REL_C
I hope this information will help you to solve this incidence.
Best Regards,
Vanessa Barth.

PO release strategy for changes in price ($ and %)

Hello,
I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %. I will need to calculate the difference in the total value between the original PO and the changed PO.
Example:
Original PO total net value is $1000
PO after a price change - total net value is $1500
Total net value has increased by $500 or 50%.
Tolerance for price change is $200 or $20, so tolerance has been exceeded.
I know I will be using the total net order value (CEKKO-GNETW). I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table. I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not. I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
What I don't know is where will I find the previous total net order value once the PO has been changed? Is the only place that information is stored in the change logs? If so, what is the change log table name? Or is there a different table that would contain this information?
Thanks in advance for any help you can provide.
Sincerely,
Angela

Update:
I utilized function module EXIT_SAPLEBND_002 as a solution to this. I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

Hello everyone,
I've run into an interesting problem:
We have defined several PO release strategies. Most of these work in the traditional manner, requiring manual approval by a given user. One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
What would cause this discrepancy? The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
Thank you ahead of time for your help.
-Jarrod

Configuration issue/user error.

Error while creating new release groups in PO release strategy

Hi All
I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
Thanks for your support.
Illan

Dear,
Please follow below mention path.
*and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
*- Follow below mention path.*
*SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
*Three steps involved in release process of purchase order.*
**Edit Characteristic     Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
**Edit Class     After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
*Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
Now see each steps of Define release procedure of purchase order in briefly: -
Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
*Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
Regards,
Mahesh Wagh

Scheduling Agreement Release Strategy Issue

Hi,
We have a typical problem in Scheduling Agreement Release Strategy.
Once the SA is released for the first time it should restart the release strategy again if there is a change in Quantity or Value or Purchasing group. The release strategy is getting restart for some of the release strategies and not for others. I compared the characteristics, class for both the release strategies and I am not seeing any difference.
Can anyone please help me in this regard.
Thanks in advance.
Regards
Ram

release strategy can be rerigger in case where qty or price change and the changes is over the percentage you defined for Release indicator
goto release indicator config and in SPRO for release strategy and check the Value change %
maintian 0.1 here
so any change above 0.1 will retrigger
and maintian value 4 in chgable field.

Problem with purchase order release strategy

Hi Guru's
    i am dealing with problem of service purchase order release strategy , when i making the service po , i am not giving any over fulfillment tolerance , after release & making Service entry sheet of PO ,   when i go to the change mode and change
over fulfillment tolerance say 90% , system allow me to make , and not applying release strategy again , so there can be a miss use of this Scenario , so is there any possibility that release strategy , will appear again when change the tolerance ,
0r any other idea from your side , to avoid this ,
your suggestions are really always helpful to me , please guide me for this also
Thanks & regards
Neha

Hi Neha,
A reset of the release strategy only takes place if
- the changeability of the release indicator is set to '4' in
   case of a purchase requisition and '4' or '6' in case of
   another purchasing document (purchase order, request for
   quotation, contract, scheduling agreement),
- the document is still subject to the previous release
   strategy,
- the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

PR Item Level Release WF not working after Release Strategy change

Hi Experts,
           I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
I really don't understand y after changing the release strategy workflow is not working and giving the following error.
Even if i restart the workflow in SWPR the same error is occuring.
Exception occurred    - Error when starting work item 000000390118
PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
CREATE                   - Error when creating a component of type 'Step'
CREATE_VIA_WFM - Agent determination for step '0000000003' failed
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
AC00000148             - Object type 'TS' not valid
Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
Regards,
Hari

Hello Hari,
please set a breakpoint at function module
ME_REL_GET_RESPONSIBLE
and see what happends in section
    CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung über T16fW
      WHEN '1'.
If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
Best wishes,
Florin

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

Deleted purchase order with release strategy

Hi all,
When PO are deleted, the release strategy is disabled. However, if you mark final invoice and delivery completed indicators, the release strategy is triggered, even if the po is deleted.
Is it possible to disable the release strategy when final invoice and delivery completed indicator are marked?
Thank you for your answer

The technical expert in my team has found the explanation to that problem:
A deleted item is "statistical" => there is no release strategy (standard control in ME_REL_STRATEGIE_EKKO function module)
But if ''final invoice'' and ''delivery completion'' are marked, the item is NOT statistical (standard control in LMEPOF4X include)
Therefore, a release strategy is redetermined even if the item is deleted
Thank you all for having tried to help

Release strategy for PO on Payment terms..

Dear friends,
Is it possible to have Release strategy for PO on Payment terms.....
I checked in CEKKO, no field availble for payment terms.
Is there any other way..........
Plz help
Rgds,
Navin

Hi,
You can append Communication Structure "CEKKO" and add Payment Term (ZTERM)
Use User Exit "M06E0004" (Changes to communication structure for release purch. doc.)
Function module "EXIT_SAPLEBND_002" (Changes to Communication Structure for Release of Purchasing)

Release strategy on PS module over budget

Similar Messages

Maybe you are looking for