Purchase order release only at header level?

Hello all,
does anyone knows a method or workaround to allow implementation a release strategy based on the positions
of a purchase order (like the posibilities in purchase requisition's customizing).
I can't find anything that helps further, only a customer development seems to be the solution.
The goal is, to route a workflow on position based cost center and account responsibilities.
There is only a field for PO release status in the table EKKO, not in EKPO. For the PR, there is a correspondig
field in the table EBAN.
Thanks for incoming answers!
Jens

Hi Diego,
sorry, my error! Thank you for your hint, but i can't find ad hoc the matching forum on sdn.
Yes, i'm talking about MM, in detail the customizing of
the purchasing process (procurement).
Best
Jens

Similar Messages

Purchase Order Total Amount at Header level and Report Execution

Dear Experts,
Here by i am facing problem with Purchase Order Total amount.
I have local Pricing Procedure for price stipulations (like discounts, Freight, packaging). the calculation at item level is correct. tax calculation is done by tax code. The total PO Price is including all items in PO and tax amount. But at header level conditions net value is showing only gross price.
How to pick up total price including tax amount at header level conditions?
Please provide me solution on it ?

Dear Experts,
Here by i am facing problem with Purchase Order Total amount.
I have local Pricing Procedure for price stipulations (like discounts, Freight, packaging). the calculation at item level is correct. tax calculation is done by tax code. The total PO Price is including all items in PO and tax amount. But at header level conditions net value is showing only gross price.
How to pick up total price including tax amount at header level conditions?
Please provide me solution on it ?
Edited by: Kiran Mujumdar on Feb 23, 2009 7:08 PM

Multi-level Purchase Order Release

Hi All,
Please help me on this.
I have already tested in QAS multi-level release but the scenario is, there's only 1 Asst Manager(AM) before. So if AM release the PO/FO, then next would be the Manager and then MM Head.
How to configure in OMGS if scenario would be the following:
Scenario 1
Amount-> 600,00 Php
Document Type -> Purchase Order
Releaser would be AM(release code 08) then M(01) then MM Head(07)
Scenario 2
Amount-> 600,00 Php
Document Type -> Framework Order
Releaser would be AM(release code 09) then M(01) then MM Head(07)
Thank you.
Best regards,
Jesielle

>
Jesielle Yanson wrote:
> Scenario 1
> Amount-> 600,00 Php
> Document Type -> Purchase Order
> Releaser would be AM(release code 08) then M(01) then MM Head(07)
>
> Scenario 2
> Amount-> 600,00 Php
> Document Type -> Framework Order
> Releaser would be AM(release code 09) then M(01) then MM Head(07)
> Jesielle
hi, there ,
if only the PO type make the difference for your scenarios then you can use standard Charateristic 'FRG_EKKO_BSART' and define two release code given assigned into two release stratage in the same release group you are in ECC6.0
regards

No of levels in purchase order release more than 8

Dear All,
We have a situation where some of our purchase orders need to be approved by more than 8 people.Can any one help me in telling-> whether we can create release strategies having more than 8 levels of approvals.If yes how to do it since I could see only max of 8 levels of approvals in the release strategy configuration for purchase order(release strategy with classification).
Regards,
Feroz Choudhury

Hello,
As mentioned by Uttkarsh, It is not possible to go beyond 8 levels in release strategy.
More than 8 levels of approval is not a best practice, if your requirement still demands this explore the options of using Workflow functionalities in ECC or if approval is complex suggest SRM where you can handle n-level approval.
Hope this helps.
Thanks
Ashu

Want to restrict the Purchase order release at lower level...

Dear Friends,
The Problem i am facing is that the release strategy defined in Purchase order is such that it will be released by four authorities,
& When 4th One, The Highest authority releases the order it should not get unreleased by lower level authorities.I want to configure this.
Partially it is completed, as if Tcode me29n is used for cancel release then it is restricted by Going into
SPRO-MM-Purchasing-Purchase Order-Release Procedure for Purchase Order- Define Release Procedure for Purchase Order
& suggesting it there.into Release Indicator
But still it can get unreleased by Tcode me28.
Kindly Suggest,
Gaurav Chopra

Hi,
This is the standard like release srtetegy will not have the restriction only the release do the release . He can also should de release the document.
this can't control.
SAM

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

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

Dead Line Monetering in Purchase Order Release Workflow

Hi Experts,
I have activated Standard Purchase Order Release workflow and it works fine now i have a requirement of Dead Line monetering for 2 days. In Standard Release Activity TS20000166 if i give 2 days in Latest End.
Will it work in such a way that if the first approvar does not take any action for 2 day then it automatically esculates to the next person in the release strategy.
Or should i use Modeled Deadline for esculation to next Level.
Regards,
Hari

Hi,
If you just have 2 days on the latest end tab, the workflow will only send a deadline notification to the current agent and WILL NOT escalate.
You have to use modelled deadline and in that branch route the workflow to the next approver based on your agent determination rules.
Satish

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

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

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 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

TWO CURRENCIES IN ONE Purchase Orders Release Procedure.

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

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

Purchase 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

With a lock item in a purchase order, release strategy works?

Dear All,
I have a very important question for myself.
I have a purchase order with only one item.
I have set this item to locked.
Release strategy works without problems.
Is this situation correct?
I don't understand it but maybe the release strategy works normally too....
Please help me with a explanation
Thanks in advance

Yes, if a release strategy is applied to a PO, then even if you block / delete an item, it will still have the release strategy.
This is standard behaviour, because you can later remove the deletion indicator or unblock the PO, whence the PO will again have to go through the Release Procedure.

Purchase order release only at header level?

Similar Messages

Maybe you are looking for