PO release strategies with Contract

Hi,
implementing a PO release strategy (SAP-MM module)I need to consider the case in which a PO is assigned to a Contract.
If so, different release strategies should be selected according to the PO value.
Possible cases:
S0-strategy 0: Contract does not exist, PO value>=0eur
S1-strategy 1: Contract exists, PO value>=100eur
S2-strategy 2: Contract exists, PO value>=200eur
Is someone aware if it is possible to activate such release strategy without defining manually in the characteristic for CEKKO-KONNR field all possible contract single values (entire range)?
Thanks a lot for helping!
Regards,
Elisabetta Rizza
Please contact me at following mail addresses:
[email protected]
[email protected]
Hi Elisabetta,
I've moved this here because it is a more appropriate thread. BPX is the place for discussing the role of the buisness process expert. This is a MM question
Message was edited by: Marilyn Pratt

Dear Amit,
Requirement: If GR posting date exceeded 45 days than delivery date set in PO, then delivery date in PO has to be changed to current system date and at the same time New Release Strategy (B1) has to be triggered with one release code (02) automatically.
So in that case the values in Release Strategy (A1) and (B1) would remain same,,, as you suggested we will assign the value 01 u2013 USRC1 to Rel Strategy (A1) and 02 u2013 USRC1 to Rel Strategy (B1) and the same we will try to incorporate in the coding of Exit u2018'M06E0004'
We will check the process and confirm the same.
Thanks for your suggestion.
regards,
Urendra Kumar

Similar Messages

Release Strategies in Purchase Order - possible values of caracteristics

Hello,
I have the following situation at hand.
We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
I can not change the caracteristics in the Release strateg because this would affect the already working strategies and SAP does not allow to asign another Class to the PO release groups.
Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
Can I use something generic in the caracteristics field of the strategy?
Thanks for any help. It would save me a lot of time!
Aart

Note 493900 - FAQ: Release Strategy
1. Question :
Why is the release strategy not determined?
Answer :
Please check the following points :
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
If you use version management, the determination of the release strategy starts when the version is completed.
You complete a version by setting the "version completed" indicator in the version tab.
Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
This is true for the other structures as well (CEKKO and CESSR). See note 52225.
For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

Are these requisition release strategies common?

All,
I’m designing new requisition release strategies for indirect requisitions at a chemical industry client. I’d like to know how often you have seen the following sorts of design before:
Existing design: Item-based release with workflow, with three dollar levels. At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic). Characteristics assign several cost centers to each approver. Strategies and codes are named for users, so we change configuration whenever someone changes jobs. The codes are linked to positions, which are attached to user IDs. Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic. A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase. I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
Thanks for your help!

Hi,
No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
For more refer a discussion:
PR release: place holder for Cost center and Material grp
NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
You can also go for other concept designing of your Requisition release strategies
Regards,
Biju K

Creation of Release order with reference to Contract

Dear experts,
We are doing upgradation from 4.6B to ECC6. During testing ,while creating release order with reference to contract,(Contract was created with Account assignment category-K and item category-D),cost center is copied from contract in purchase order in account assignment tab of item details,
but when i save it window is poping up(account assignment service line item 10-small window) asking to enter cost center again. Even if i enter the same cost center in that window,cost center field,again it is asking same window is poping up for entering cost center.
Can any body please tell me inspite of cost center is copied,why this window is coming ,please suggest.This problem is not there in 4.6B version
Advance thanks,
Regards,
Dayanand

Please check to OXK1, and compare it to both system.Or check the config guide in IMGMM-Purchasingacc.assigment--Set subscreen for acc assingment (coding) block.

Purchase requisition : problem with check release Strategies

Hi all,
i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
Is there a special value to give the release indicator 'released' ?
Thanks for your help.
Edited by: ToraTora on Mar 31, 2011 5:46 PM

Hi,
Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
select release indicator
by default, you will be having the following release indicators in the system,
1     Request for quotation
2     RFQ/purchase order
3     RFQ/PO no change of date
4     RFQ/PO no changes
A     Fixed RFQ
B     Fixed RFQ/purchase order
X     Blocked
please check whether you have got these or else create and then assign them to the release strategies.

ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

Problems with the Losing Release Strategies Approvals in PO.

Hi Experts,
We're using the BBP_WFL_APPROV_BADI for Purchase Orders (WS14000145) the source code of BADI works fine.
I can define all the approvers as source code.
I'm making any text modification in the PO with status Awaiting Approval. This works fine, but I have a problems when i make the modification in the PO ( Document Approved ) with status ordered or Error in Process , if I make the simple modification (explo. text modification) the release strategie is re-starting again, losing all the approvers and approvalls. We need that modification not start the release strategy again.
The re-start should be make only for values modifications (Price, Quantity).
There is other problem with approvals preview too, the approval's preview with the ordering of approvals dissapears. When
I make the same modification in PO with ordered status.
Thanks

Hi Masa, How are you?
I check the table BBPD_COMP_FIELDS but i didnt understand anything...I need to make tho desactivate the re-start of release strategies..WHen I make a smple modification in the PO ( for explo text documents).
I my process now..if I make the modification in the PO with status orderer ( any modification) the system re-start the approvals levels...I need re-start only for value modifications...Could you help me?
Thanks,
Gustavo Nogueira

Release Strategies - Integration with users

Hi All
How to integrate users with release strategies for a PO?
i.e., I have 3 Level release strategy and 3 users(Purchase executive, Purchase Manager, Finance Manager)
Regards
Jagadish

Hi
You need to assign the Rlease codes to the users, in the authorisation profiles.
In the role for authprization of transaction ME28, you have the authorisation object , in which you assign the release codes to the user
please take help of basis consultant in role creation
Thanks & Regards
Kishore

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Release PO against contract whit limit value for USER

Dear colleague,
We work SRM server 5.5 . SP14 extended classic scenario, and we use contract management.
We need to release PO against contract and we want to LIMIT the users that PO value have to be between 60 USD as minimum order value and 120 USD as maximum order value.
We know that solution for the minimum order value is to use the u2018minimum order valueu2019 in the contract item with the value 60.
Can someone help with the solution to limit user to maximum order value against contract.
Thanks
B.R.
Gil shinar

One option is that you could implement the maximum value logic in BADI BBP_DOC_CHECK_BADI and give out proper error message if the user enters value outside of the range.

Open Order quantity in Release order of Contracts

Hi all,
We are developing new PO format for Release Order ( Contract) where in we want to print the Open order quantity & Open order value along with Contract number.
What is the best logic for Open order quantity, where in it has consider all the previous release order quantities minus the target quantity in contract.
Open order quantity = target quantity in contract - all previously release order quantities.
Thanks in advance.
MM
MM

hai sajid,
As u said,
open order quantity = total quantity in contract - total quantity released against that contract ( Through release orders )
it is right,
with regards
srinivas

Function Module to find out the release value in contract

Dear All,
I have to upload the contract with new accoutn assignment without changing the existing contract. For that i have to download all the existing contract data with value.
In that case i have some issues regarding the value.
For example : In the system old contract is created with value 1000 and the released value as 500.
In that case i have to uload the new contract with all the details of existing contract with value of 500 (1000-500=500).
How can i get the value (500) and from which table.Is there any functional module to find out the release value in contract.
Thanks and regads,
PM
Edited by: PM on Jan 21, 2010 8:40 AM
Edited by: PM on Jan 22, 2010 9:48 AM

Hi
You need to link the table VBFA and VBAK.
For a contract you can check all the subsequent document (which you can filter whether you want to see Order / delivery / Billing) in VBFA and then from there pick the subsequent document no. and then from VBAK you can pick the Net value of these subsequent documents, and so you will have both the values (value of Contract and value in subsequent document) and you can determine the balance value.
Regards
Amitesh Anand

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

Release strategy with classfication & w/o classfication problem

Hello guys
I am facing problem in setting up the release strategy . ECC 6,0 came up default without classification. we need with classification. i set up w/o classification, then delete it and then did with classification.. it works fine for me in the Sand Box , but in dev server it didn't work for me. It is working only w/o classification , When i am trying to set up with classification , it didn't work for me , i am getting the error message in the check release strategy as follows . How i can find which release group need to create ?
Any help will be highly appreciated
Thanks
N
Release code for release group is inconsistent
Message no. ME_RELCHK057
Diagnosis
The release code is not allowed because the associated release group no longer exists.
Procedure
1. Recreate release group .
Note
The release codes and release strategies for a release group are only displayed if the release group still exists. Therefore you must create release group in order to delete the release codes and release strategies.
2. If necessary, delete the release strategies and the release codes for release group .
3. Then delete release group .

Hi,
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated. The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
To set up a release procedure with classification, you please delete all entries in the Release codes and Release Groups for Purchasing Requisitions and start a fresh creation of new Release Codes and Release Groups.
Hope you have followed the following procedure:
1. Create characteristics and classes
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
2. Define organizational plan
3. Assign standard tasks and activate event-receiver linkage.
4. Set up release procedure with classification
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a release point
5. Check release strategies
Hope, this time you will be able to perform the PR Release with Clasiification.
Regards,
Narayana.

PO release strategies with Contract

Similar Messages

Maybe you are looking for