Pr& po -new release strategy? released/locked/incomplete
Dear MM experts,
I would like to understand what it is meaning of
released
locked
incomplete
while doing assignment of object class thru cl24n for new release strategies,
I am clear on released & locked, I would like to understand what is "incomplete" means as per SAP.
kindly clarify
thanks in advance
srihari
Incomplete means - When you go to CL02 or CT04
you are entering the statu for calss or char as locked or released
but when you are creating and that time if you have keep the status is in preparation and without changing the status you start maintainig the data in CL24N than you will see the statu as incomplete.
Similar Messages
-
Scheduling agreement Release strategy release indicator
Hi all
For the Scheduling aggreement Release strategy is present & release indicator is 6 , Now the requirement is whenever user is changing the any value Scheduling agrrement it should go for rerelease. for any minor change in value even the value lies between the same Release strategy
Release strategy is configured on Purchase group & Value character
Also what is the difference between release indicator 4 & 6. for any changes in the SLA release strategy will be reset in this two release indicator.
Thanks & Regards,
RajeshHi,
This is a standard phenomena any change in value (increase)will reset the release stategy
and indicator 4 & 6 are same only in case od indicator 6 if you have taken the oout also it will get affected -
Old PR release strategy - release completed status change
Dear Gurus,
We have impletemented Item level release strategy for PR.
There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
Please advice
Regards
RSHi,
Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
Check the value of Changeability of purchasing document during/after release ( 1 - 6).
Choose the appropriate value based on your req.
Regards,
Udayasankar Rajagopalan
Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM -
PO release strategy - release code
Hi Experts,
I have completed the release strategy and transported to production.
However noticed that the release codes that has been configured earlier wasn't in the production.
Is there a way to update the release codes in the production besides using SPRO (no authorisation for maintaining - only display) like using CL24N to update the characteristics?
Thanks and regardsHi,
Please first check the attached notes that refer to transport issues.
365604 FAQ: Release strategies in purchasing
186809 OMGQ/CL24: Inconsistency for release strategy class
86900 Transport of Release strategies (OMGQ,OMGS)
45951 Transporting class data: system / client
10745 Copying classification data to another client
The classification data must be sent over using ALE. It does not get
transported directly. Notes 45951, 86900 and note 365604 should help.
Please follow the instructions in note 45951.
You can obtain more information about how to set-up ALE in the Online
Documentation CD (R/3 Library > CA - Cross Aplication Components >
Business Framework Architecture > ALE Integration Technology > ALE Quick
start).
However, if you can't set-up ALE, you can re-create the classification
data agin in your target system. For that you have to:
1- assign new values to the characteristic master data (t-code CT02)
2- assign the new data to the classification system (t-code CL30)
3- verify the consistency with t-code CL24. Please see note 186809.
For more information, please see note 365604.
The transport of release procedure customizing data can only be done
in a restricted manner. Please take a look at attached Note 86900 and
follow the procedure described in this note, in order to correctly
transport your release strategies.
Classification data can only be transported via ALE as per note 45951.
Note 45951 explains what class data for the release strategy will be
distributed from one system to another. It does not describe how to
implement as this involves a lot of explanation and is truely a
consulting issue.
There is another possibility that you could take into consideration for
the classification is to import them via batch input:
RCCTBI01 for creating characteristics
RCCLBi01 for creating classes
RCCLBI03 for classification
Best Regards,
Arminda Jack -
PO Release strategy release procedure
Hi
Any body can suggest
what is the procedure for release strategy transport to anther system means D to QHi,
Release strtagy Configuration can be transported from one client to various client[Like creation Class,characterstic,Release code,release strtagy definations etc]
Where as assignments of Objects / class and various parameter for release strategy has to be done in individual clients in -T-code: CL24N.
Example : For Class -PO Release we need to assign -Values for Class -characteristic values has to assign in CL24N
with regards
Shrinivas Gangoor
Edited by: Shrinivas Gangoor on May 22, 2009 3:06 PM -
Pr& po -new release strategy?
Hi Friends,
My requirement is to add new release strategy for pr & po.
Characteristics & Class are remain unchanged.
Pl advise to how to proceed, i mean
i have to set/create new release procedure, ie.,
New release groups
New release codes (bcos new codes are added & release levels remained same)
New release strategies
How i can retain the Old PRs & POs released with earlier release strategy/release codes?
PRs & POs not released can be with new release strategy, but i have to ensure the old prs & pos (released) were with earlier release strategy & release code.
Also, I need ur advise, how the new release strategy works for workflow
pl help
thanks & regards
SrihariHi,
First of all, if you would only like to create the new release strategies, then the only possible settings you should do are -
1) Create the new release code;
2) Create the new release strategy;
3) Assign the release characteristics values to your new release strategy in CL20N transaction.
For those old PRs and POs (regardless of if they were released or pending for release), the same old release strategy remains unchanged (and therefore, you should be much careful if you wish to delete the outstanding release codes and/or release strategies through configuration). Having said that if you would like to keep the same release strategy though changes are to be made to your old purchasing documents, then you will have to assign the proper value to the "Changeability" field of your "released" release indicator.
In case of release strategy in support by workflow, basically, the workflow item will be triggered (in accordance with the pre-defined logics that you built in terms of task ID). As soon as the approver determination is made in background, the workflow item will be then sent to such agent who will then take a proper decision (approve, reject or forward).
Cheers,
HT -
How to setup a release strategy for store generated purchase order
Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2teaPlease go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok -
Purchase Order not subject to release strategy
Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisahhi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 0
1
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
regards
ravikant dewangan -
Hi Friends,
I have a issue to fix. The issue is releated to PR.
There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
I have to retrigger the release strategy for all the affected PR's.
The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
Regards,
Manjunath KHi,
Refer the discussion to triggers release again on release code addition/change in release strategy.
release code is changed on PR release strategy - old PR can´t be approved
Regards,
Biju K -
Mm pr-po release strategy : error
Dear MM experts,
We already having MM-rel strategy for PR & PO with classification procedure and working fine,
Now business requirement is to change the MM-Rel PR& PO strategy,
New mm-rel strategy for PR customised in class 032 (not to use existing release groups & release strategies)
After doing config settings in customising client, the request moved to another client for testing.
Testing client, request moved successful, and while checking the settings in testing client,
in Release Strategies - details mode
Informatination is available at Release pre-requisites, Release Statuses without any error,
but when we try for Classification, we are getting the following error
"Error in classification (class PRREL class type 032)"
Can u please suggest what needs to be done so that we can go ahead further.
Kindly note while doing config setting client, we did not encounter the above error, it has accepted all the settings (copy existing rel group & having differnt rel strategies, etc)
pl help
Thanks in advance
SrihariHi Friends,
My requirement is to add new release strategy for pr & po.
Characteristics & Class are remain unchanged.
Pl advise to how to proceed, i mean
i have to set/create new release procedure, ie.,
New release groups
New release codes (bcos new codes are added & release levels remained same)
New release strategies
How i can retain the Old PRs & POs released with earlier release strategy/release codes?
PRs & POs not released can be with new release strategy, but i have to ensure the old prs & pos (released) were with earlier release strategy & release code.
Also, I need ur advise, how the new release strategy works for workflow
pl help
thanks & regards
Srihari -
PR Release Strategy Re-determining due to Change in Text
The PR release strategy was configured by a previous company. There are existing PRs that are not completely approved (Release Indicator = 2). The SAP instanced was transitioned to the company that broke away.
The PR release has now been re-configured with new release strategies (groups, codes..etc). What we are experiencing is that the existing PRs that are "released" do not show the new release strategy when the combination of release strategy/release group does not exist- This OK as well.
When a user made a change to the Item Text and nothing else, SAP re-determined the release strategy and started the release process over again. Is there a way to stop these PRs from re-determining and therefore restarting?Hi There
Though the release strategy is different, i think all the classifications are same or old classification (even 4 or 5 parameters) may also part of your new full release strategy(You may be trimmed from old release).
So when you do any changes or just go to the change mode and Check (F7) , system may find the new rel strategy.
i have not tested the above scenario, i could recall some older posting based on that i did suggest the above
Thanks Senthil P -
Hi Guys ,
I have a work flow requirement , In Which i have to know in Purchase requisition items history . how to identify the new item and
change items for triggering the work flow .
Here i am using a badi to triger an event . ( BADI : ME_REQ_POSTED )
Any idea , Plz share .
THanks
NagsHi,
First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
For Work flow settings,You have to do follwoing configuration:
MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
Creation of work flow object,activation of workflow and other related settings will be done by Techinical work flow consulant.
Thanks,
AMIT -
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
chandooThis is the workflow forum.
-
Overall Purchase requisition Release strategy : Changed after Rejected
Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev -
Work flow for release strategy for PO & PR
Hi Gurus
Can anybody explain workflow for release strategy for PO and PR
Thanks in advance.
Atul KulkarniHi,
First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
For Work flow settings,You have to do follwoing configuration:
MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
Creation of work flow object,activation of workflow and other related settings will be done by Techinical work flow consulant.
Thanks,
AMIT -
FB60/FB65 Release Strategy
Hi All,
While processing the transaction code FB60 / FB65, we need the system to check a Ztable which contains the maximum tolerance limit for employees to process the invoice / credit memo. The system should give a warning message and send email to the supervisor about this.
Though we could locate an user exit for this purpose, please advice if we have standard release strategy / release procedure / workflow which can be used for this purpose.
Kindly revert back with your ideas as soon as possible.
Regards,
Sanjay.Sanjay,
the process is present with tolerance groups in tcode OBA4
you don't need a customer table and a "hidden sending of an e-mail"
regards
Andreas
Maybe you are looking for
-
A few weeks ago I found I could no longer work on my bank account site. I can still access the site and see the balance of my various accounts, but as soon as i try to do anything like go to the bill pay or transfer funds, nothing happens. I have had
-
My ipod nano isn't syncing when I try and change the setting in manually, but is however syncing when I launch the itunes by plugging it in. I'm wondering if anyone has had this issue and/or had been able to fix the problem?
-
This is the story. Up until two days ago, when I completed a video project in Final Cut Pro 10.0.9, I went to file->share->YouTube and a window opened up that showed the name of my YouTube account - (e.g., account.name) which is the same as the name
-
Hi Team, It is a regular requirement to have the requestid kind of functionality of the BI/BW to be had it BPC. i.e who did what and when. I haven't completely thought abt the whole step by step process....but here i
-
Is there a good Mac Metadata editor? I have an oddity in some files - the time listings are way off - 2:30 songs are listed as 11:00 minutes. I would just re-rip them except these are Cd's that the label reissued to replicate the original 45 vinyl si