Release Strategy in Procurement?

Hi,
When I create a PR, there is a release procedure based on the release code, release group, plant and the price.
If a release is 'IN PROGRESS' status or 'RELEASE REFUSED' status, i would like to know which user was the last person to have released it or cancelled it. How do I know in which table this data is stored.
I am unable to map it and i have had a look at EBAN,EBKN,T16FW,T16FD,T16FC & T16FS, but i am unable to figure out which table stores the values of the users who have cancelled or released a PR.
Regards,
Thiru

Hi,
Please try the BAPI
BAPI_PAYMENTREQUEST_GETSTATUS
or
BAPI_OBJCL_GETSTATUS (pass the Object Number for the PR)
or the Function Modules from Function Group BSVA like
STATUS_OBJECT_READ
STATUS_READ
Hope it helps....
Lokesh
Pls. reward appropriate points

Similar Messages

Release Strategy of Procurement in BI Content?

Hi,
Is there any standard datasource about Release Strategy of Procurement in BI Content?
Any helpful suggestion, I will give points.
Thanks.
Stephen

There are couple of approaches that can be taken with this issue since there are delivered extracters exclusively for Purchasing Requisitions.
1) Piggy back on PO ITEM Extracter (2LIS_02_ITM) or PO Schedule Line Extracter (2LIS_02_SCL).
Purchasing Requisition/Items (Table EBAN, TCODE ME53) are uniquely linked to PO/Item (Tables EKPO, TCODE ME23N).
PO Item (EKPO-EBELN & EKPO-EBELP) are linked to (EBAN-BANFN & EBAN-BNFPO).
Based on this you can extract the required fields from EBAN in the User Exit for PO ITM or PO SCL extracter.
This is what I did but my case was not same as yours. We primarily need PO Item/SCL information with some pertinent attributes from the requisitions
Pros: No need to write a seperate extracter.
Cons: If there are any requisitions that are not converted to PO's they will not be included in extraction till such time they are actually converted to PO's
2) As Bala indicated , Create a Custom extracter based on Table EBAN.
Pros: All Requisitions are extracted regardless of whether they have been converted to PO's.
Cons:
1) I am not certain if Generic Delta will successfully trigger all Changes to the Requisitions (depending on how the P2P process is configured for your Project).
2) If Delta does'ent work in all scenarios then a FULL load might be very difficult to manage based on the Data Volume.
Hope this helps.
Thanks
Vasu

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

SES Release Strategy not invoked in Backend from SRM confirmation posting

Hi,
I have configured a SES release strategy based on vendor number in R/3. When a SES is created in R/3 via ML81N the release strategy is invoked as expected. However, when a confirmation is entered in SRM for that vendor, the SES that is created in the backend system is created in accepted status and the release strategy is not invoked.
Can anyone advise how to get this to work the same way as ML81N?
I would expect that the SES would be created in the backend from the confirmation without acceptance and the release procedure to be the same as ML81N.
thanks,
Michelle.

Hi,
The SRM confirmation in EBP is the goods receipt(MIGO) and not the service entry sheet entry (ML81N) as we do in Materials management.
As per my understanding there is no provision of service entry sheet entry in SRM 5.0 as of now and SRM 7.0 has this option coming up :
In SRM 7.0 ,
"Supplier-maintained confirmation (service entry sheet) for services performed based on the service items within a purchase order
Confirmation supporting hierarchical structure of service items"
are added.
Look for this information in the thread which speaks about SRM 7.0
Re: Benefits of upgrading to SAP SRM 2007
which gives the info in slide 11, Delta SRM 7.0, Service procurement -2
Best regards,
Sridhar.

EPRTRANS - PR items release strategy

Hi gurus,
I'm working in SRM 5.0, ECS, backend ECC 6.0.
I need to set up the 'Plan Driven Procurement scenario'.
In ECC I created entries in V_T160EX and V_T160PR and I have mantained TBE11 and TBE31 accordingly to SAP note 656597.
I used ME51N to create a purchase requisition (without items release strategy) which is getting copied to EPRTRANS table.
A purchase requisitions (with items release strategy) is getting copied to EPRTRANS table when I Save the PR?
or when I release the single items?
Points will be rewarded
Thanks in advance
Gg

Hi Disha,
you said:
The table EPRTRANS will be populated only when all the items(which have a release strategy) in the PR will be released.
Do you mean that if a PR contains two items (both with release strategy) and only the first has been released, EPRTRANS will not be populated until I release the second item?
Is that correct?
Thanks in advance
Points will be rewarded
Gg

Release strategy - item level

hii all
can some body tel me , how and where we have to configuration for PR release strategy at item overview level.
And the same item level release strategy is posssible to configure for PO also??
If not y what is reason???
Thanks in advance
SAP-MM

hi
> how and where we have to configuration for PR release strategy at item overview level.
http://www.sapstudymaterials.com/2008/08/purchase-requisition-pr-release.html
>And the same item level release strategy is posssible to configure for PO also??
hi we cant have itemised release for PO
logically thinking PR can have multiple item and no fixed vendors and even not sure for placing order
so the realing person will decide for the item to be purchase so it has itemised relase
now in PO ,u will raise PO only when u have confirmed the purchase and the order will be for one vendor
so for ordering u have to relese the whole po,
or u can say u will create PO for all the items which have to procure so release will be for whole PO
go to spro>MM>Purchase Requisition>Release Procedure read the left side help for WITH and WITHOUT CLASSIFICATION
Edited by: Kunal Ingale on Mar 9, 2010 6:32 AM

Contract Release Strategy - field Requisitioner

Hello,
I will start to use the Contract release strategy and I need the field Requisitioner (EKPO-AFNAM), because this field is part of my PO release strategy.
This field isn't available in the transactions ME31K and ME32K.
Can you tell me, if it's possible to show it in these transactions?
In other case, where can I fill this field? How is the BAPI, BADI, etc?
Thank you,
Meire

Hi,
Please, be so kind to refer to note 373361. This field was only
available in purchase requisitions and due to requirements of
SRM (formerly BBP business tons business procurement ), it has
been added into the new enjoy transaction
ME21N/22N/23N for purchase orders.
It is not available for contracts.
The contract is not the last document in the procurement.In bussiness
process the requirement of requisitioner in contract is less important.
It is enough if you don't know the requisitioner at the time of contract but
you know it at the time of PO creation.
This is the standard SAP design.   Please do not use this field in the contract release strategy: create a new release group for the contract release strategy, delete the value entry for EKPO-AFNAM in the "Change view - release strategies - classificaion". The characteristic for EKPO-AFNAM should appear as black and not as blue on the screen. Save your strategy.
Regards,
Edit

Reg PO Release Strategy

Firstly Release strategy for PO is configured.
Now they are asking for new release codes to be added to the old ones.
The issue is when i am configuring this
old PO's no probelm as they are released.
new PO's no problem.
The issue is with OPEN PO'S .The new release code is going and sitting there but no PEN MARK will be there.(It is simply GRAYED OUT).so this creating problem for OPEN PO's.
How to overcome this.
with regards,
Patil Mallik

You didnot understand my problem.the problem is suppose there are 3 release codes previously.now only 2 release codes has released the PO.Still one release code yet to release.
now if i configure the new release strategy with one more New Release code.That New release code will come and sit in this Open PO(whose two release has happened and waiting for 3rd release) without having Pen symbol to release it is infact grayed out.
This should not happen i think.
for this there is any solution.this wont effect my procurement process.but the job of 4th new release code is done by 3rd release code which is not correct at the time of audit etc etc.
Any work around for this.welcome your suggestions and answers.
with regards,
Patil Mallik

Release Strategy Disapearing

Dear Experts,
We have two plants 1000 and 2000.we configured release strategy for both plants.
when we create Po against one plant the release strategy is working,but when procure the
material in one PO with 1000 and 2000 plants,the release strategy is disappearing,is it SAP
standard only,is right practice to create a Po against two plants.
Regards,
Varun

Hi,
This is not a good practice, Donu2019t create a common PO for both the plants.
Regards,
Karthick

Stop release strategy when pgrp changed triggering different release group/

Currently when our buyers change the purchasing group field on the purchase requisition it is triggering a new release strategy because the release group and code is different than the original creator.
It has been indicated that we should request from SAP that these two fields be made available to the structure for the release strategy.
Is there a user exit that we can use to stop a new release strategy?

Hi,
Do you have different rel. stgy for diff. plants? if yes, than which rel. stgy should be picked in case if both plants entered have different rel. stgy? what is your expectations/requirements?
If your PO is to go through diff. approvals for different plants than you should have different PO for each plant (even diff authorizations and rel. codes), or else you should not have plant as the criteria. Technically, whether it is fesible or not is different question, but whether practically your organization is ready that if a common material is to be procured it will have approvals of only one plant or may be a different approvals all together?
Regards,
Dakshesh

PR Release Strategy tab processor field is not getting displayed

Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandoo

This is the workflow forum.

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

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.

PO Release strategy

Hi,
I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
Any suggestions are highly appreciated to fix this issue.
Regards
Sudhakar

Hello,
After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
regards
anand

Release Strategy in Procurement?

Similar Messages

Maybe you are looking for