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 Kulkarni
Hi,
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
Similar Messages
-
Work flow in release strategy..?
Hi experts
Can anybody expalin me what is Work flow in release strategy .
Exaplain me with some examples for Work flow in release strategy.
Thanks
SAP-mmYou have to carry on the following activites:
1) Define Organisation Struture
2) Application specific customizing
A) Define Characteristic values
B) Define release codes and make them Workflow relevant
C) Define release strategy
Based on the characteristic values the Purchase Order will be applied to a particular release
strategy and will fall under specific catagory to pass through different level of approvals
D) Assign release codes to corresponding Orgnisational Objects with ID
3) Task specific customizing
A) Activate the event linkage for the standard workflow WS20000075
B) Do the agent assignment for the TS20000166
C) Make other two tasks as General Tasks (TS20000168,TS20000167).
4) Delete the row for event "Releasestepcreated" from SWEC (OSS Notes: 797775)
Hope this will help you -
Customizing steps of workflow for Release strategy
Hi Experts,
Iam looking for step by step customizing details of workflow for Release Strategy for Purchase Requisition.
I need necessary classification and Customizing settings for a release procedure in the purchase requisition to the workflow.
I am looking for the steps, in which the purchase requisition can be edited straight from the workflow inbox.
Regards
NaniHi Nani,
First you have to confirm what kind of release it is in Purchase req you have Item level release and over all release.
Item level release - WS00000038
Over all Release - WS20000077
Now please confirm with your MM consultant that he has done the release Strategy and tesed it Ok.
Escecially things like assigning plant, Assigning Agents,Release codes and so on when everything is done by him in SPRO.
Now your work starts If it is just release use the standard workflow.
If they need additional notification mails and things like that copy the standard workflow and do the customization in the copied version and deactivate the standard workflow.
You can also do dead line monitering (Factory Calander) and many more things.
also please go through these 2 links you will get better idea.
http://www.****************/Tutorials/Workflow/POReleaseStrategy/Details.htm
http://www.****************/Tutorials/Workflow/PRRelease/PRRelease1.htm
If you have any othere queries please feel to ask.
Regards,
Dheepak
Edited by: dheepak on Dec 1, 2008 7:48 PM -
Workflow for release strategy in PO
Dear All,
Will anybody tell me how to configure the workflow for release strategy for PO.
Regards
R PandaDear Manish,
I have done all the configuration as per your guidance.
But I am not getting the mail in mail box. I have done the following config
Gr Cd WF Descrip
02 I6 1 HOD Logistics-JSR
02 I7 1 GM Logistics-JSR
Gr Cd Descrip OT Agent it
02 I6 HOD Logistics-JSR US RP
02 I7 GM Logistics-JSR US DD
OOCU---
MM-PUR
1) Activate event linking- WS 20000075---BUS2012-RELEASESTEPCREATED-ACTIVATED (I ticked both the check boxes)
Linkage status-no errors error feedback---system defaults
2) Assign agents----WS 20000075Create agent assignments-I assigned above two user ids against user......
In attributes it was no general task & not classified.
In trxn code SWETYPV both the check boxes are ticked with no error.
Please reply.
Regards
R Panda -
Release strategy for PREQs created from PM work order
Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
DesislavaHi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj -
User exit for Release Strategy in PM Work Order
Dear all,
Please help me with the following issue:
My client want to change the approval route of the release strategy of the Work Order. The release is based on the PM Activity Type. Now, I am brand new on the project, I have no documentation and I have no access to CMOD so I don't know where to find the cusomised release strategy for change it.
Please, can you advise on this?
Thank you very much.
SorinDear,
to have release strategy based on "PM ACTIVITY TYPE", i suggest you two ways
Option-1:
1) Have permit system with classification as per the approval hierarchy.Create permits as per approval levels.
2) Once maintenance order is created, system will assign the permits to that maintenance order at the time of saving.
3) Now approvers will approve the permit with respect to Maintenance order PM activity type.
Note: If your client wants to have mailing functionality to their out look or other mails, put logic in save exit after assignment of permits to maintenance order, with the help of ABAPER and also the sequence of approving the permits.
Option-2:
1) Create user status profile as per approval hierarchy with number assignment.
2) Create "Authorization code" for the user status number.
3) Provide "Authorization code" to the SAP user ids as per approval hierarchy.
or
If you have only one app rover, provide authorization of creating order to one user and "Releasing" the order to other user.
Regards,
pardhu -
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. -
Release strategy for quantity contract
Hi Gurus,
In quantity contract .. target value will not filled by the value(in header details) as it is quantityt contract.
We may have different line items with different cost..
my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
please explain/clarify
regards
subbuHi,
The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined based upon the total net value of the entire purchasing document.
Cheers,
HT -
Release Strategy for Contract is not getting picked whereas it is ok for PO
Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
SatishS0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you -
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. -
Reset Release Strategy for any change in the Purchase Order
Hi,
Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
If so, where do we need to make the configurations.
I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
Thanks in Advance.
S.Raghavanhi sandesh,
sorry, i know it's too late.
i tried your suggestion, it works blocking the purchase order after release strategies are setted.
sandesh, raghavan:
i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
regards
f -
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 contracts.
Hi gurus,
Good day,.
Please help on this.
We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
Example.
Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
Thank you.Dear Acel,
The example you given was working just fine and correct.
a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
-> The release strategy will only be reset if the total net value for the contract was higher the previous
value but not lower.
As your example, quantity was updated to 1200, then it will reset when changing from 1000
to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
In system, it always assume if you had approved for the total value of the higher 1 before, then
it should be fine for the lower total net value for your management and therefore not need to re-approve
again for redundancy job. This was very logic in common business scenario in many companies.
However, like in your example , if you had define a different release strategy for a value that met the
the 1100 quantity, it will redermine the different release strategy. For example:
USD 1 for every quantity = 1
Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
USD 1200 for quantity = 1200.
Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
Release strategy C for 1200 , characteristics from USD 1200 onwards
Then if you change the quantity from 1200 to 1100, it will redetermine the release
strategy B which means from Release strategy C to Release strategy B. If you
only had Release strategy C that had a characteristics from 1000-1200, then
it will keep the Release strategy C as released and it won't be reset unless
if you had change it and the condition of the total net value was higher than any value
before.
Hope this will explain the logic.
Ian Wong -
Release strategy for PO, RFQ & Contract
Hi,
We have created release strategy for PO, RFQ & Contract.
Characterisitc is created for Target Value for Header Area (CEKKO-KTWRT)
for RFQ & Contract it working fine but for PO not triggering.
what can be the cause.
Pls guide.Hi,
Melih is right, for POs you can not use the target value.
What you might do is to include the document type and CEKKO-GNETW as additional characteristics and then set for contract document types the GNETW blank, and for PO documet type the target value blank. Blank means any value should fit.
I hope this hint helps!
Best Regards,
Arminda Jack -
MM:Release Strategy for Release Order again Approved Contract
Hi,
Release strategy for Release Order is required or not against approved contrat??
As fas as I know once the contract is approved, release order is not required to approve again.
This is the standard setting from SAP or We need to do some setting for this??
In my support project I have studied the release procedure and found that, same release strategy and release Group has been used for Purchase Order and Contract.
Please let me know if anyone have faced this rquirement or I have to go for Z development for this requirement.
Thanks you.Hi Lalita,
Thank you for your quick suggestion.
yes definitely the release stratergy and release group should be set up separately but here both are same
that is the reason this is picking of the same release procedure again evenif the contract is approved.
we have following release characterstic for the release procedure.
1) Purchasing Group
2)Total Net Order Value
3)Order Type
4)Purchase Organisation
5)Material Group.
I think for the above characterstic we must a separater value for PO and Contract but Currently all are merge
in this only
But Can you tell me "Release Order should be subjected to release procedure" this is correct or not .
If yes then what is the base for this, I mean is it working on the concept that " If do relevent
release characterstic value is found then no release procedure and this is treated as autorelease in sap"
Thanks you.
Maybe you are looking for
-
Confirm Production on any open production order
Hello Gurus. Our company receives material at the end of the production line and they need to report this production in the system. The problem is that at this point, they don't know what Production Order it relates to. Is there a transaction in SAP
-
Message F5A034 - SCB indicator in FB60
Hi All, For Germany customer/vendor invoices in a foreign currency, we need to specify the nature of the transaction (State central bank and the country) we have done System Landscape optimisation and in the source system, they are getting the mess
-
Another PPC/Intel node question!!!
Hi MacAddicts, I've searched the forum but didn't get an answer about this. I want to connect a PowerBook(host)to an Intel Mac mini as the node(the poor man's HD setup!!). I'm on LP 7.1.1 on Panther. Can i install the node app. from 7.1.1 on the inte
-
How to accept Intel wireless license without adding kernel paramenter
Is it possible to accept the Intel wireless license without having to amend my kernel boot parameters? Perhaps a way to accept it permanently? It seems inelegant to me to have to add a boot parameter to my kernel in Grub in order to use my integrated
-
Hi as of CAF's nature, reusability must be an essential characteristic of CAF Service. Just imagine a business expert wants to find an action in GP to validate a product catalog sent in the format of an european standard, say BME, such task just invo