Which PO value is picked in Purchase Order Release Strategy?

I have one query-
My Material Cost PBxx is 5000/-
My VAT/any tax ZBNQ is 500/-
Suppose I have set up Rel Strategy as PO value less than or equal to 5000/- R1 and Po value greater than 5000/- as R2, the system is showing me as R1 instead of r2.
What to do in this case?

> My Material Cost PBxx is 5000/-
> My VAT/any tax ZBNQ is 500/-
>
> Suppose I have set up Rel Strategy as PO value less than or equal to 5000/- R1 and Po value greater than 5000/- as R2, the system is showing me as R1 instead of r2.
Hi Ajay,
System triggers release based on the JEXS condition type value in case of tax code at the item level. In your case it is correctly triggering. However it will trigger based on the sum of line items at the header level.
Revert any further queries
Regards,
Shiva

Similar Messages

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

Purchase order release strategy with a characteristic value as a variable

Hi all,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
a few other custom fields
We would like to add a characteristic based on the creator of the PO. In the purchasing department there are two person which have the authorization to create an release POs. The goal is now to check if the actual user, who release the PO, is different from the PO creator. The value of this characteristic may not be a fix value, it must be contain the name of the actual user name.
Is there are a possibility to insert the characteristic value as a variable such as SY-UNAME instead a fix value?
Thanks,
Charles

this is verymuch possible. You can use unsed fields user1, user2 etc in CEKKO or (ii) insert a new field in CEKKOZZ and use the new field. You need to build up logic in user-exit such that this field will take the value of person who had logged in. This can be done by ABAPer.
Hope this resolves ur problem

Purchase order release strategy with multiple characteristics

Hi All,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
Release strategy Type
a few other custom fields
We would like to have PO's with release strategy based on a particular Material Group [say X]. I have created a new Characteristic with respect to CEKKO-MATKL and added this characteristic to the same class.
I have created a new release code [HR] [we need a different person to sign off] and a new release strategy [TR] for which I have assigned the release code HR. In this release strategy, I have set it to get activated for a particular Material Group that does seem to work, but the remaining PO's are not getting triggered for other material groups. For other release strategies, I have left the material group field blank, because they need to be triggered for any material groups except X.
Could you please let me know if I am missing something or is there an alternate approach to this ?
Thank you,
Satish

Hi,
Obviously system will not trigger release strategy in ur case since in the classification data for other strategies u have left it blank excepting X for one strategy.
Since u have added a new characteristic Material group and assigned it to class then system expects an input for Material group for triggering release tab.If this is left blank then system by default will not trigger release strategy tab.
Solution:
First add all existing material groups in values tab of mat group characteristic then maintain the required set of material groups except X in other strategies in classification data.
Hope this is clear to you.
Regards,
Uzair

Purchase order release strategy report

Dear Gurus,
We are using purchase order release strategy with classification.
We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
How to get it ?
Please provide ur help for the same
Rgds,
Saurabh

Hi,
Basically in EKKO table there is a field name FRGZU -
Release status based on that we can write a logic take the report.
for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
Just tell him the logic to ABAP person they will develop
Rehgards
Murugan J

Graphical view in Purchase order release strategy

Hi Experts,
I have added new position in existing Purchase order release strategy which is running properly.
I am facing the problem of visual display in header on tab release stratege for the PO which are already released by respective authority.
It is showing final release balance all though release indicator set to "1".
For e.g.
PO number 123 was released by 4 persons in past.
As per new modification release agencies are 5 nos.
for this PO release flag set to "1"
As 4 persons involved in PO release the graphical display shows 5 agencies for release but release tick infront of these show only 4.
My Problem is client wants correction in this graphical display.
Please help me on this.
Regards
Dhananjay

TELL THE SOLUTION DEAR ..SO ANOTHER WOULD GET HELP IN FUTURE.
REGRDS
MANOJ

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.

Purchase Order Release Strategy Approval

HI All,
I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
Level one will have 1 approver
Level two must have two approvers.
The scene is:
Level one will approve all purchase orders betwee 400 to 5000 euros. 1 approver only
Level two will approve all purchase orders above 5000 euros. 2 approvers.
The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
Pur. group G70, Release Group GC and release strategy DF.
I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
CL20N is completed for both levels and works correctly for level one approval but not for level two
Can any please help
Leslie

Hi,
May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
1. PO Order Type (ZPO_BSART),
2. Company Code (ZPO_ BUKRS),
3. Purchasing Organization (ZPO_EKORG),
4.Plant (ZPO_WERKS)
5. Purchasing Group (ZPO_ EKGRP) and
6. Total net PO Value (ZPO_GNETW)
Create one release class ZPO_CLASS & then add all above release characteristics
And then design your release strategies as required.
AND under release characteristic for PO Value (ZPO_GNETW) keep following values
A. <= 400 EUR
B. 400.01- 5000 EUR
C. >5000 EUR
As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
Regards,
Bijju K

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

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

Workflow - Purchase order Release strategy

Hi All,
Good Morning
I had created workflow for Purchase order release strategy with steps(To Determine Agents, Release of Purchase order, Release of PO effected) and in Me21N I created PO and PO came to my SAP inbox(SBWP) and I released that PO and saved it.
but My problem is after releasing PO when I checked my Inbox again still that PO is sitting there, it is supposed to disappear from there
Can anyone please assist me to resolve this issue .
Thanks in advance.

Hi,
In standard SAP workflow, SAP is sending a mail item (notification) to SAP mail inbox. There is no action is required from there. So mail will remain their as mark as read. If you want to remove it than one needs to delete it from respective mail box.
Best Regards,
Bhagat

User Exit for Purchase Requistion / Purchase Order Release Strategy

Hi
Can any one please tell me the List of User Exit / Enchancement Package for Purchase Requisition / Purchase Order Release Strategy .
Thanks

M06B0001
Role determination for release of requisitions
M06B0001
Changes to communication structure for release of requisitions
M06B0005
Changes to communication structure for overall release of purchase
requisitions
M06E0004
Changes to communication structure for release of purchasing document
M06E0005
Role determination for release of purchasing documents

Purchase Order Release Strategy with Dependency Condition

Hi
We have a scenario where we have to set up Purchase Order Release based on a combination of the following
Vendor + Purch Org + Dollar Value.
We have successfully set up the release strategy for which we have done the following
1) Create Characterstics for Vendor, Purch Org and Net Order Value
2) Assign the above characterstics to a Class
3) Assign Class to the Release Strategy in SPRO.
So far everything is good.
Now we try to define a Condition. With a Fourth Characterstic (TRIG_RELEASE ) attached to the same class.
And attached a Dependency condition to it.
$SELF.TRIG_RELEASE = 'Y' IF VENDOR = '1000' and PURC_ORG ='8500' and NET_VALUE > 1000.
When this dependency is set, the release doesnt trigger.
but modifying the condition to
$SELF.TRIG_RELEASE = 'Y' IF VENDOR = '1000' and PURC_ORG ='8500' .
Trigger the Release for that condition.
How can we base the dependency on Net Value also ? What are we doing wrong or missing ?
Regards
Aju Paul

Hi Paul,
I'm not sure why you really need that fourth characteristics. In my opinion, the three characteristics are good enough to achieve the desired release strategy. Why don't you just create a strategy that has those specifc characteristics value in your classification.
You can do that from SPRO or CL24N.
Define a new strategy in SPRO e.g "Vendor 1000 Porg 8500 > 1000"
In CL24N, enter the class name; e.g Z_PO_RELEASE.
class type 032
Hit the enter key for existing release strategies to be displayed. Select the one you one just created above. Then click on detail and your characteristics/Value is displayed below.
Then maintain the different values for the charateristics and then test with PO creation
Xtic                  Value
Vendor                1000
P.Org                  8500
Value                  > 1000

Purchase order -- release strategy

Dear Friends,
I have a requirement for Purchase order Release.
The problem area is in purchase order ... there will be 2 Relase approvals
01 Mr. Abcd
02 Mr. Xyz
After level 1 approval and before level 2 approval ... i want to do some actions.. these actions are related to another product named savvion .
My question is can i stop the document to be edited by 02 ( Mr.Xyz ) untill i complete my process after 01( Mr.Abcd ) has finished his work.
This is to be done on top priority.
Please help me.
Cheers
Jitesh.

Hi,
Yes, We can stop the document to be edited by 02 until 01 has finished his work.
After 01 approved the document need to be correct, go to PO header menu release strategy TAB and 01 approved to be revoked (means double click on the tick mark, it will revoked).
Hope it is useful for you.
Regards,
K.Rajendran

Purchase Order Release Strategy - Emails/SOST

Hi,
Please bear with me in terms of knowledge level on this subject, it's not normally my "area" but I'm trying to assist a colleague.
When an order reaches a certain value, it requires authorisation by a senior member of staff, from Manager to Director, and finally Managing Director. Probably not unusual.
When a member of our Purchasing Team input an order that requires higher level authorisation, after it has been authorised it goes into the email queue in SOST.
However, the sender is displayed as the person who authorised the order, not the person who raised the order. In other words, we have Purchase Orders arriving in Vendors inboxes addressed from our MD!
We don't want this.
Can anyone point me in the direction of the config which may allow me to alter this?
Many thanks.
If this is in the wrong forum, I apologise, I was unsure where to post it.

this can only be achieved with a modification.
Please find details in OSS note 561593

Which PO value is picked in Purchase Order Release Strategy?

Similar Messages

Maybe you are looking for