Release Strategy for New Plant
Dear All,
I have a Release strategy in my 3 Plants and it is working fine.
Now I want to add one more plant under the same release strategy.
I tried to add the new Plant in CL24N. System allows me to add the same in this but the RS is not working in this new Plant.
waiting for reply
hi,
you follow the following steps to insert new characteristics value in your release procedure.
1. define the new characteristics value plant4 in your characteristics.
2. assign the same characteristics value plant4 in classification of release strategy.
3. run the release simulation and comes out.
4. now create PO for your requirment and save it.
5. u can use me22n/23n to view your release status of po.
hope it helps....
manoj singh
Similar Messages
-
Release Strategy for New & Change PO's - Using characteristic CEKKO-REVNO
Hi All,
I have the following requirement/scenario
1. If PO is created manually no reference to PR, then the PO needs to be approved through a release strategy.
2. If the PO has been created automatically either from a req or through SRM (for,eg) then the PO needs to be approved only if this PO has been changed. So this would need to go through a second release strategy.
To distinguish between the two, we are using Version number field CEKKO-REVNO in the communication structure CEKKO to be a characteristic in the release strategy.
This is what I hoped for would work after doing the necessary config,
For create PO's, in my classification I have CEKKO-REVNO as >=0. So any PO whose version number is >=0, will trigger relase strategy S1 (for e,g).
For change PO's in my classification I have CEKKO-REVNO > 0 And whenever you change PO, it will generate versions 1,2,3 and so on, and hence the release strategy will trigger.
The problem
Whenever I use CEKKO-REVNO as one of my characteristics, the release strategy is not triggered at all no matter what the conditions are on the PO. When i removed the REVNO from my classification, release strategy is getting triggered as per plan. I have also activated version management and done all the necessary config. I would like to know why release strategy is not getting triggered when REVNO field is used from communication structure CEKKO. Have any of you experienced this issue before??
Is their any other identifier I can use to address the requirement above? Let me know.
Thanks
AshvinThanks Charlie for your response.
The conditions in the PO is not equal.
On one occasion when I create the PO, I have given the classification as REVNO >=0 with a document type ZB for create (S1). So when I create the PO manually, the version starts with 0, so condition should satisfy here
On the other when I change the PO (with/without reference to PR), I have given the classification as REVNO as > 0 with document type ZC (S2), so when the PO is created initially it will not satisfy strategy S1 as doc type is different for S1. When I change the PO created with ref to req, S2 should take into effect because when i change the version will change to 1 and S2 should trigger because REVNO is > 0 and doc type matches.
So I dont know where the release strategy matches in both S1 & S2 for the system to not propose the release startegy.
Let me know your thoughts.
Thanks for your feedback. -
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 -
Release Strategy for SA/Contract/PO
Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
PrabhuHi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards -
Release Streatgy for multiple plants
Hi All,
I have one PO with multiple Item having different Plants.
For Each plant i have a release streatgy with different release codes for each plant and in release streatgy i put characterstics like
1. Plant
2. Value
3. Purchase Organisation
4. Document Type.
Now my Question is that when i use mutliple plants for different line items of one PO.
How will my release streagty will work ? and how it should be configured ?
Regards,
Pardeep MalikHi,
Your Release strategy will not work.
In you want to get the release strategy for multiple plant then you have to define another strategy in OMGS u2013 say 01 u2013 07 as Multiple plant and for that strategy in CL24n mating all the characteristics and donu2019t maintain any value for your characteristics plant and then check.
Try it its very helpful -
Release Strategy for a new material type in PR
Dear Friends,
One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
Regards,
AskHi,
Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
Then follow all the cusmozation path for your PR release startegy .
For Config part refer the below wiki link it may help you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808 -
Release Strategy with New Class and Char.
Dear All,
I have facing problem when creating the new release strategy for different country. i have create new Characteristic and class for new Release streategy.
when i going to add in Release group.. system giving the error.
Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
My existing Characteristic for india :
ZP0_GNETW Total net order value CURR 15 2 INR
ZPO_BSART Order type (Purchasing) CHAR 4 0
ZPO_EKORG Purchasing Organization CHAR 4 0
ZPO_EKGRP Purchasing group CHAR 3 0
New Characteristic for South africa :
ZPOSA_BSART PO Order Type ATSA CHAR 4 0
ZPOSA_EKGRP Purchasing Group ATSA CHAR 3 0
ZPOSA_EKORG Purchasing Organization ATSA CHAR 4 0
ZPOSA_GNETW Total net PO value ATSA CURR 15 2 ZAR
ZPOSA_WERKS Plant CHAR 4 0
Please help me how do configure 2 release strategy for 2 country.
I will be very thankfull to u.
Regards,
Vishal GargHI Biju K,
I can use exising Characteristic Like Purchasing Organization & Purchasing Group & Plant etc. But in the case of Net order value : ZPO_GNETW Total net PO value for my indian company Currency is INR and for My SA company currency is ZAR. What will i do in that case.
Please explain..
And aslo clear the concept of creation of new Characteristic as Company Code & design different release strategies based on company code. How i can do that..??
Please explain in details.
I will be highly thankfull to u.
Regards,
Vishal Garg
9810402156 -
Removal of plant from P/R release strategy of another plant
Dear Friends,
In our office there are two plants P068 & P281 both belongs to two separate co codes. In its P/r release strategy in characteristics plants are mentioned so for each plant their should be separate p/r as they are located differently. But unfortunately plant P281 is added in the release strategy of plant P068 though there is a separate release strategy configured for plant P281. So while making P/r of plant P281 release strategy of plant P068 is getting called & the user is not able to release the same because of the restricted authorizations. We have tried to remove the plant P281for which we created the request on DEV server & transported to PRD server but this is not removed. It is still reflecting in P068 P/r release strategy. Kindly advise how we can remove this ? Is their any other alternative way?
Rgds
Prashant BYou need to remove the plant from classification of release strategy. If system is modifiable, go into release strategy and classification and uncheck the plant, which is not required and save.
OR
If backend is unmodifiable, use this t-code CL20n/CL24n, put in the release code strategy combination and in the classification remove the plant of it and then save and your problem will be solved.
Follow the above steps for adding the plant to new release strategy as well.
Edited by: Afshad Irani on Apr 28, 2010 4:45 PM -
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 adviceFirst 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. -
Want to change my existing Release strategy for - PR, PO & Service Entry
Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vbDear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy -
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 -
Release strategy for PO and RO
Hi All
My release strategy for Purchase order and Release Order is same.My release strategy has material group and PO/RO value as characteristics. What I want is that my releaase strategy for PO should be based on value whereas for RO it should be based on material group. Is this possible since we cannot have different release group for PO and RO.
Pl suggest how to go about?HI Satish,
In the characteristic value screen we not only can give single values ,but also multiple values
and also range of values.
Since the Data type for this Feild is character ,that is the reason it is not taking Ranges
So the same is not working for PO,I too Checked the same.
So it is that you have to have material group ,then there is no other go but entering all the values for the same.
As we cant add a new Release Class also
Becoz the release class cant be different ,so as the characteristic values would be same.
if i could find something else will post you soon.
but as of know we cant do nothing in this case but create all the material group as charecterics values and add to that strategy.
Thanks
Anjanna. -
Release strategy for Future validity period- (Outline agreements)
Dear All,
I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
How to set up release strategy in the above case.
Thanks in Advance.
Regards
AmarHi Amar,
1) if you maintain a target value (EKKO-KTWRT) in the header of the
contract this value is the basis for the determination of the release
strategy. If the target value is 0, the system will cumulate the
values of the items and will use this value for the determination.
2) So if the target value is 0 and you change the price of a condition
with a validity period in the future the system will react in the
following way:
Example:
the contract contains one item with quantity = 100 and a net price
of EUR 5,-.
all contracts with a target value from EUR 0 - 1.000,- should be
subject of a release strategy
the contract is created and released on October the 1st
ME32K -> October the 2nd you define a new price of EUR 7,- with a
validity period from 03.10.09 - 30-10.09 -> you save the contract
-> the release strategy is not reset, as the start date is not
reached yet (system date < startdate of validity period)
ME32K October the 3rd you change a field in the contract -> the
release strategy is reset
This is system design that a release strategy can only be reset through
an action by the user. The determination of the release strategy can't
be triggered automatically in the background.
If you create a document which is subject of an overall release strategy
(e.g. p.o., contract) the determination of the release strategy takes
place when the user hits the 'save' button or chooses the 'check'
function.
So there must be a kind of event that tells the system that something
has changed.
Regards,
Edit -
Release strategy for auto created PO's
Hi Guys,
I have a requirement to implement release strategy for automatically created PO's.
PR's are created automatically and we have a program which create PO's automatically.
we would want to release them before generating output to vendor.
could anyone please have any inputs here.
regards
mittuHi!
You may use your existing release strategy or create a new one (depending on your requirement). You just have to add/ use the document type you used for your auto-generated POs.
Hope this helps! =) -
No release strategy for service PO
Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
ShailendraKeep the release strategy at Plant level only....All the purchasing docs will get blocked
Maybe you are looking for
-
My laptop has recently broke and is not able to use in any way. I had an Ipod and an Ipad both connected to the itunes on this computer and have purchased a new laptop. However, after downloading itunes i tried to sync my devices with it but it told
-
I am having difficulty deleting a project that has no photos in it. When I try to delete it, I get the message: "This operation will delete the project "" and all of its contents from your library. Managed master files stored in the Aperture Library
-
[HELP] iPhone 5 KEEPS REBOOTING!
Hi guys, I have my iPhone 5 in February this year, but now it kept rebooting since last week. I have my phone restored to the newest OS and even set it as a new phone. But the problem still is there. And I checked the real-time system Log generated f
-
Parallel portal implementation in a non-unicode landscape
Hi All, We have existing 3 system landscape with 3 systems in it. DEVQASPRD.All of these systems are non-unicode. The java add-in cannot be installed on them because the unicode java stack cannot talk to nonunicode abap stack.The customer does not wa
-
Plug ins for Preview (Leopard)
Are there any plug-ins (or scripts) for Preview? I want to add an image or a text field to a PDF. (OSX 10.5.8)