Trouble shooting Purchase requstion Release stratergy with classification

Hi,
I am trying tos Set up a release startergy for Purchase requistion items with classification
I am trying to capture Requestions with the following characteristics.
Purchasing document type (ref to CEBAN -BSART)
Total Item Value (ref to CEBAN-GSWRT)
Purchasing group (ref to CEBAN-EKGRP)
I have set up the release stratergy. However when I create a requisition with the criteria matching the release stratergy the PO does not get activated.
I want to see what Charactersitics my PR has at runtime so that I can try to reslove the issue.Does anyone know of a transaction or report I can check to see what charatersitics my PR picks at runtime?
Thanks,
Ishan.

Hi,
Go into trx CL30N and enter the values of the document :
1.If you don't get a result> check in customizing definition of release strategy and check
In trx OLME > PR > define document type 
"Overall release of purchase requisitions" flag ( fiield V_T161-GSFRG ) should not be SET
In TRX OLME > OR > release staregy > Release Groups
also FRGFG should not be set
2. If you get one result> check
If  you have activated the userexit 'EXIT_SAPLEBND_001'
(Include ZXM06U13) This exit is relevant for the individual release.
If you activating the userexit, please ensure that you implement
the coding line E_CEBAN = I_CEBAN. in the include or deactivate the
exit. Please refer to point 3) of the note 365604.
BR
Nadia Olrandi

Similar Messages

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

  • 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

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

  • Purchase order Release Stratergy-Error in Class CL01

    Purchase Order Release Stratergy:
    In CL01(create class) i have created the class FRG_EKKO and saved.Then in CL02(change class) under Basic data-Administrative data we found Assignment field tick is not selected and that is not in changeable mode.
    Because of that reason Error occured like Error in Class in SPRO release stratergy. Release is taking place in Development Server but not in Production server.
    Regards,
    Wilson Babu G

    Hi
    This indicator shows that objects are assigned to this class.
    The indicator is set automatically by the system.
    once you assign the class to any objects then this flag will come automatically.
    Please check if you have assigned the characteristics to the Class in CL02
    Please check if you have assigned the release strategy to the Class in CL24N
    Thanks & Regards
    Kishore

  • 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

  • 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 procedure with classification not getting triggered

    Hi,
    I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
    Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
    Your suggestion would be highly appreciated.
    sachin

    Hi Jurgen,
    I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
    Where as I did the same setting for PO, its working and giving me correct releaes strategy.
    My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
    Please suggest me on this.
    sahcin
    Edited by: sachin sagane on May 18, 2010 6:32 PM

  • Purchase Requistion Release Stratergy

    Hi,
    I have a situation where I need to get the details of the classification Net total in purchase Requistion for the particluar Release Stratergy and Release Group from the relevant table for raising an event manually in work flow, which I am uable to trace out.Please help in this regard for identifying the tables which holds the data of the Net value for the same.
    Thanks in Advance for your Help
    Regards,
    Krishna Mukthineni

    Hi Krishna,
    the classifications of the release strategy is best read via the API (interfaces) for the class system. To get quick results and to check, if your designed process could be working at all, you could hard-code the class' name and it's characteristics. Later on -- to be more precisely -- you should read the class name from the customizing and the characteristic definition from the class system.
    To get an example of how SAP determines the release strategy from the classification (which is kinda the other way round), you may consult the following function modules/coding sections:
    Function module ME_REL_COM_STRATEGY_EBAN
    --> Form strategie_neu
    ->-> Function module CLSC_SELECT_OBJECTS
    To see the usage of this function module within your system, you could set a break-point there and create/change a requisition in your system.
    The internal table iausp holds the values of the characteristics.
    The referenced characteristic you'll be possibly looking for is based on CEKKO-GNETW
    Best regards,
    Florin

  • PR Release Stgy - With Classification & Without Classification -Difference?

    Hi
    Pls tell me the concept behind this and the difference
    Vijay

    Hi ,
    In without classification only four characterstics are allowed and they are
    account assignment category
    material group
    plant
    purchase requisition value
    Where as without classification you have more flexibilty and almost all the fields in table EBAN can be used for setting up Release strategy ( Also we can have release strategy at item as well as  at header level in with classification  )
    Regards
    Ankur

  • Predefined object type for Purchase order release stratergy

    dear experts,
    There are already predefined object type for purchase order like bus2012 where i can create new events and methods. I want to know is there any predefined objects for purchase order release strategy. The requirement is there i want to define method, that should display the po release screen. If i bind this method with work flow template, mail should be triggered and if i click the mail po release screen should be opened for respective material...
    regards,
    Kandhan G

    Hello
    I'm using the BUS2012 Object type in workflow task but in simulation the task run correct but in the transaction when modify a purchase orden the task send an error...
    maybe the error is similar...did you solve this problem?..
    Thanks!
    Wladimir E.
    [email protected]

  • Purchase Requisition release WF with multi-level release strategy

    Since it has been "a while" from my WF course and i lack experience with WF's (this is supposed to be the 1st one i implement, finally)...
    The problem I'm facing is really in planning phase of sketching up how my scenario should look like. I have to create couple of WFs for a project that involve purchase requisitions and purchase orders.
    The problem i'm trying to solve is logic concerning release strategy steps for this documents. They are set-up and well-deffined in customizing, but there are couple ofrelease steps for particular strategy.
    Scenario:
    1. someone creates a purchase requisition (event for BUS2009 is triggered, and workitem appears for release of Purch. Req. in their workplace)
    2. initiator of workflow executes his workitem and selects one of the release codes (this workitem is now complete) - i'd like for new workitem to appear in supervisors inbox automatically...
    3. now i need supervisor of initiator to release same purch. requisition with another release code (how to do it?)
    4. supervisor of supervisor (mentioned in step 3.) needs has the authorisation for final release with final release code.
    5. now the initiator from step 1. has to be notified that requisition has been released by overall head of department.
    Org structure i created looks like this:
    ORG. UNIT. Level 0 for Purch. Req. (with Head CEO of Plant as final approver)
    ORG.Unit.  Level 1 for Purch. Req. (with Head of level 1)
    ORG.Unit.  Level 2 for Purch. Req. (with Head of level 2 and Clerks 2a,b,c)
    So these guys (Clerk) 2a,b,c create Purch.Req. They or their Head of level 2 releases their requisitions with his release code Z1,
    Head of level 1 should recieve workitem in his inbox to be able to release it with his release code Z2.
    Director of the plant should recieve workitem for final release Z3, after Head 2 did his release with Z2, and then guys 2a,b,c should get notifications that their PR's are released.
    I managed to get the SAP's standard for Purch. Req. Release working but it's just not enough...
    Please advise me, guide me, if u have any idea, how could this be done, because i'm loosing a lot of time here, just searching and not seeing it. The problem is that we don't have any WF experienced guys that could help, so i'm kinda' stuck.
    Could standard be used here at all?
    Is it possible that the same task (for example. TS00007986 - Release requisition) appears more than once in the sam WF with different agent asignments?
    I dont have an idea how this scenario should be built in WF builder.
    BTW, i'll have 12-15 plants, does that mean 15 different WFs and Org Units?
    Help WF gurus.
    Thank you in advance,
    BaX

    Its' a while since I last time worked with PRs, but I'll give a try...
    This part is a bit confusing:
    >1. someone creates a purchase requisition (event for BUS2009 is triggered, and >workitem appears for release of Purch. Req. in their workplace)
    >2. initiator of workflow executes his workitem and selects one of the release >codes (this workitem is now complete) - i'd like for new workitem to appear in >supervisors inbox automatically...
    >3. now i need supervisor of initiator to release same purch. requisition with >another release code (how to do it?)
    Why do you want that the initiator (the creator of the PR) needs to go the business workplace and release the PR (or select the release code). Isn't this an unncessary step? Shouldn't it worked like this:
    1. Someone creates a PR
    2. PR "gets" a release code automatically with some logic defined in customization
    3. PR release work item apears in the supervisor's  workplace
    4. Initiator gets the mail
    If I recall correctly, the standard solution works like this, or has quite similar approach.
    Whatever way you decide to build your workflow, you won't most probably need a workflow for each plant, but you'll need several org units. But this all really depens on how you decide to do it...

  • Purchase order release strategy with a characteristic value as a variable

    Hi all,
    We have Purchase order release strategy based on the following characteristics:
    Total Net Order Value
    Purchasing Organization
    a few other custom fields
    We would like to add a characteristic based on the creator of the PO. In the purchasing department there are two person which have the authorization to create an release POs. The goal is now to check if the actual user, who release the PO, is different from the PO creator. The value of this characteristic may not be a fix value, it must be contain the name of the actual user name.
    Is there are a possibility to insert the characteristic value as a variable such as SY-UNAME instead a fix value?
    Thanks,
    Charles

    this is verymuch possible.  You can use unsed fields user1, user2 etc in CEKKO or (ii) insert a new field in CEKKOZZ and use the new field.  You need to build up logic in user-exit such that this field will take the value of person who had logged in. This can be done by ABAPer.
    Hope this resolves ur problem

Maybe you are looking for