Re: PR Release Strategy with workflow

Hi Expert,
   Is there a way the scenario given  below will be possible to achieve..
   All the needed config for the  PR release strategy has been define... (release code, group,release strategy,class & characteristic)
  Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager  ( Release Code :PM)
  The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
  9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

hi
i think u need workflow for release strategy
Steps involved are :
1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
3) Go to OOCU > here under MM, go to MM-PUR,
4) Click on "activate event linking"
5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
and Save.
6) Click on "Assign agents" and proceed all above steps.
BUS2012 is the relevant business object and Releasestep created is the event for the same.
7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
take help of ur BASIS person
hope it clears
regards
kunal

Similar Messages

  • Release Strategy with Workflow for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Hi Swamy,
    The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
    How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
    Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
    How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
    How to configure?
    Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
    For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
    For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
    Maintain the details u already have in hand:
    For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO.  After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
    Hope this will give you an idea how the workflow works and how to configure it.
    Rgds.

  • Purchase Order Release Strategy with Workflow

    Hello Experts
       In activity Release Codes workflow column has 3 options.
    (1) Blank  =  No workflow
    (2) 1  =  Role resolution with group, code and plant
    (3) 2  =  Role resolution via user exit
    Can any one explaing in detail what is difference between option (2) & (3)?
    Thanks
    Ankit

    The difference is obvious. In option 2 your workflow will decide the approver based on Release Group, Code and workflow object assignment. In case of option 3, your workflow will decided the approver based on the rules coded in User-exit.

  • Release Strategy and workflow in Purchase Requisition

    Hello All,
    My client wants to activate the release strategy and workflow at the purch req and PO levels. They allow users to create a Preq and reference that preq to the PO, or users may create a PO without referencing a Preq. Since they have the release strategy and workflow working on both levels, what they want done is, if a PO has a Preq reference, it does not need to go through another approval process on the PO level as it has already been approved on the Preq level. Therefore if a Preq is reference in a PO, the PO workflow and release strategy should not be taken into account. Can this happen as a standard config, or will this need a "user exit"?
    Thanks in advance for your help!!

    You will need to activate the user exit. This will keep the PO release strategy simple.
    Have a flag (use USRC1 or USRN1). In your PO release strategy classification, maintain only X in this characteristic.
    In the user exit, check whether the PO is created with reference to PR. If yes, pass "blank" to USRC1, else pass "X". The release will be triggered only in case of X.
    Just a couple of points:
    1) What will you do if one item in PO is created with reference to PR and the another item is not?
    2) What will you do if one item is partially referenced to PR (i.e PR quantity is 100, PO quantity is 200 - of which 100 is referenced to PR and other 100 is not - this is possible by changing in delivery schedule)?
    Hope this helps
    Lakshman

  • Purchase Requisition Release Strategy with classification

    Hi there,
    Please help,
    I have the release strategy and workflow working. (Overall Release)
    Problem is that Org Structure is not updated so workflow has been configure going to (US) user. As i am using workflow option 1 which is resolved via Group, Code & Plant, I have to have a code for every region and manager to resolve the workflow. I am not using plant as business requirement is overall release.
    Scenario is that there are 8 regions with 1 senior region manager and 1 executive.
    The region managers can each release up to 20k. Senior region manager must release from 20k - 50k. Executive must release from 50k -250k.
    Release Codes:
    Regions = L1 - L8
    Senior Region Manager = SR
    Executive = X1
    Characteristics are:
    DocType = NB
    AccAsingment = K (Cost Centre requisitions)
    Purchasing Group = (Each region has own group)
    TotValue = 0k -20k, 20k - 50k, 50k - 250k.
    Now the release strategies.
    Even though it is the same senior manager and executive why do i have to create a new strategy for every region's escalation above 20k taking into account that the business requirement is that the correct region manager has to release before the senior manager can release? It just seems so pedantic when i would rather just add the correct Purchasing Group everytime.
    This is only one leg of the Org Structure there are over 40 depts, and managers that will create and release. Do i really need a strategy for every single scenario?
    Thanks for taking the time to read.

    Hello,
    Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
    Cheers !

  • Release strategy  in workflow

    how to use release strategy in workflow for purchase order?
    regards
    rose

    For all of you : This is the best you will get: go through and sit with your functional consultant to understand the process.<a href="http://help.sap.com/saphelp_47x200/helpdata/en/1d/ea9d9c7aca11d194b70000e82dec10/frameset.htm">http://help.sap.com/saphelp_47x200/helpdata/en/1d/ea9d9c7aca11d194b70000e82dec10/frameset.htm</a>

  • Creating Roles for Purchase Req. release strategy with classification

    Hi friends,
    Since I have created Purchase req rel strategy where I have four release strategy
    1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
    2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
    Now the manager will have 2 release code,if  officer is absent he could release the requisition.
    Same has to be done for plant 2
    The release Group and code needs to be assigned to the Roles , could anybody tell  me  where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
    though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
    1. For Plant 1 lower value of requisition 1 codeL1(Officer)
    2  For higher value of requisition 2 code say Li and L2(Manager)
    Manager should have 2 codes if  officer is absent he could release
    Same has to be done for Plant 2
    Thanks N Regards
    Siddhartha

    Hii,
    Steps:
    1) Create a Role
    2) Add the authorization Object  M_EINK_FRG by taking the manual option
    3) Assign Release Code and Release Grp
    4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
    Regards,
    Kumar

  • Tranposrt - Purchase Requisition Release Strategy with Classification

    Gurus!
    Tell me if I want to Transport the Purchase Requisition release strategy with classification. The Data in each charisteristics in each PR Strategy that I have set in Dev is not getting transported to Quality.
    Do I have to enter the data in characteristics again in Quality and the same procedure I have to apply for Production.
    If yes, in this scenario, Can I make Production modifiable.
    Regards
    Sajid

    Hello,
    Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
    Cheers !

  • How to control PO Release strategy using WorkFlow

    please tell me how to control PO Release strategy using WorkFlow.
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on May 31, 2011 9:35 AM

    Hi,
    Yes they are same unless you differentiate by using
    1> Purchasing Document Category i.e CEKKO -BSTYP
    A.....     Request for Quotation
    F......Purchase Order
    K......Contract
    L......Scheduling Agreement
    So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

  • PR overall release strategy with acc. assignment category characteristics

    Hi,
    Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
    see below more details :
    I have created the following PR release strategy with classification.
    PR type concerned " NB": overall release
    Rlease group concerned : overall release
    In this release group i have 1 class
    in this class i have 2 characteristics : PR type and Account assignement category.
    Release strategy 1 :
    PR type = NB
    Acc. assignment cat = P, W
    Release strategy 2:
    PR type = NB
    Acc. assignment cat = K, V
    TEST 1 : PR type NB, 1 item with P category
    OK the release strategy 1 is generated
    TEST 2 : PR type NB, 1 item with W category
    OK the release strategy 1 is generated
    TEST 3 : PR type NB, 2 items with P category
    OK the release strategy 1 is generated
    TEST 4 : PR type NB, 2 items with P and W category
    TEST KO, no release strategy is generated
    => what should i do to solve this issue ?
    Thank you in advance for your quick answers,
    Isabelle

    What is the specific requirement for Overall release strategy?
    Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
    Every line item generates a PO, so logically should be set to a release strategy.
    Bottomline is use release strategy at line item level Unless a specific reason exists.
    Regards,
    Sameer

  • PR release strategy with classification

    As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
    The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
    Any pointers to solve this will be highly appreciated.

    Hi Ashish,
    If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
    Regards,
    Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM

  • MM Release Strategy with Cost Centre

    My characteristics for the release strategy is Accnt Assigmnt (KNTTP), Cost Centre (KOSTL) and Amount (GSWRT). I link all to the ceban straucture, and for the cost centre, I entered in the value tab the cost centres that I am using, and I entered the cost centres in the release strategy. Everything seem OK for the release strategy, but the release strategy is only selecting the strategy according to the values and not considering the cost centre, what can I do let it consider the cost centre and the value. I have been struggleing with this problem more than a week now. I tried everything that I can think of. Can someone assit me in this matter. I am on ECC 6.
    Thank you.

    Refer OSS Note :: 52225
    Solution ::
    Summary
    Symptom
    Purchase requisition release strategy with classification does not work as expected when the characteristic for cost center KOSTL is included.
    Message  ME297 is displayed.
    Additional key words
    CEBAN-KOSTL, KOSTL, Cost center, Release strategy, OMGQ, ME297
    ME51, ME52, ME53
    Cause and prerequisites
    Numeric values used for the cost center characteristic in the purchase requisition release strategy with classification is not recognized. CEBAN-KOSTL is a CHAR field of length 10.
    Solution
    Enter leading zeros for the cost center value in the release strategy. eg. If the cost center value is 123456, while entering this value for the cost center in the release strategy, enter it as 0000123456.
    Cheers !!!!!!
    Biswajit

  • Release Strategy With Classification

    Hey All,
    I would like to get some information about release strategy with classification for purchase requisation and purchase order.
    Please send me some information  regarding this.
    Thanks
    Kawal

    hi,
    To see the all the linkages firstly see the classifcation and class defined in the sap system at:
    SAP easy access --> Cross application components --> classification system --> master data --> characteristics and classes(CT04 and CL02)...
    TO see the customisation, check:
    Spro --> MM --> Purchasing --> PO/PR etc --> Release procedure --> Rel procedure with classification --> Here check for all the different transactions...like Relase codes, release stategy, access sequence, schema etc...
    Also one important point abt it is:
    PR is possible to release at header as well as at item level...
    But PO and other external docs are only possible to release at header level only...
    In the customisation check all the linkages you will get best out of it....
    Regards
    Priyanka.P

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

  • Issue: Purchase order release strategy with storage loaction.

    Hi Friends,
    I have created release strategy for purchase order considering following characteristics.
    1. Plant
    2. Purchase organization
    3. Purchase group
    4. Document type
    Hence the release strategy is working fine.
    Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
    Can any one tell me how to maintain this LGORT filed in structure CEKKO.
    Thanks in advance
    Shashidhar

    HI Shashi ,
      Thanks for your quick response,
    I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
    Also we written the code :move:  i_cekko = e_cekko, in user User-Exit M06E0004 function exit
    FUNCTION EXIT_SAPLEBND_002.
    However, the release strategy is not triggering when PO is saved,
    also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
    in it.
    Kindly reply.
    Thanks  ,
    Shashidhar

Maybe you are looking for

  • Boot Back Into Windows With Boot Camp

    Hello, I am running Boot Camp on a Mac Book Pro. It runs extremely well except for one issue. When the mac goes to sleep for a short time minutes to a few hours, and I click a button, the Windows screen is there ready to use. But, if it sleeps over n

  • Embedding Youtube Videos Inside Blog Comments

    Is there any way to embed a YouTube video inside the "Comment" field on the iWeb podcast or blog page? I want users to be able to embed videos of their choosing as comments, rather than to have to post them (which takes more space), or simply link to

  • How do I transfer photos from my ipad to my iphoto library?

    I synced my my ipad to my mac and now 3 events are missing from my iphoto library, but are on my ipad, weird!  can I sync it with my mac and will the photos return to my iphoto library?  I'm affraid to sync it now after what happened I'm affraid to l

  • IPhoto on iPhone never completes Updating Photo Library

    Tried about 10 times. After opening iPhoto, it attempts to Update Photo Library. It gets about 3/4 way done and then quits. (I do have a LOT of photos, probably about 20,000 on my phone) iPhone 4S 64GB, IOS 5.1

  • How do I convert Spreadsheet file to Waveform for off-line analysis?

    Using v6.1 I have multiple column data in an xls file obtained from third party DDE write. Each column contains data pertaining to one process variable. Does not include timestamp, however, data sampled at specific frequency of 10hz. I wish to conver