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

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 !

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

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • Badi for Purchase Requisition Release Strategy

    Can any help me to know about the BADI for Purchase Requisition Release Strategy .Is their any BADI to  control the PO Price for a PR release strategy
    Thanks for your help

    This badi is for schedule agreement ?
    BAdI: Release Creation for Scheduling Agreements with Release Documentation
    Use
    You can use this Business Add-In (BAdI) to influence release creation.
    This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).
    This BAdI includes the following methods:
    Change Data Before Release Creation (BEFORE_CREATION)
    Change Data After Release Creation (AFTER_CREATION)
    This BAdI is called during manual and automatic release creation.

  • 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

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

  • Workflow for purchase requisition release strategy

    Hi all,
    I need an urgent help on Workflow for Purchase Requisition Release. The requirement is that when a purchase requisition with a given combination (Purchasing Group, Material Group and Account Assignment Category) is created and saved, it should trigger a workflow for approval of release or rejection to one specific business manager. If he dont responds in 2 days, it should be sent to other business manager. If any one of them releases the requisition, it should send a mail to the requestor that the requisition is released. And if it is rejected, then also a mail to be sent to the requester informing that his requisition is rejected...
    Can anyone take some pain and guide me step by step procedure to implement this or to use any existing one.... I know its BUS2009 thats used in this but really dont know how to implement it properly.
    Its urgent...
    Edited by: Hima on Apr 11, 2008 12:45 PM

    Check this link
    http://help.sap.com/saphelp_47x200/helpdata/en/04/92762546f311d189470000e829fbbd/frameset.htm
    Thanks
    Arghadip

  • 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

  • Creating  workflow for purchase order release.

    Hi friends
    I want step by step detail about creation of workflow for purchase order release..
    After release purchase order it will goes to the two level of approval..
    after that the workflow should be completed...
    how can i develope the workflow for that scenario..
    Thanks
    Gowrishankar

    Hi Gowrishankar,
    You can get step by step workflow for PO using standard workflow
    <b>Release of Purchase Order :WS20000075</b>
    And for two levels of approvals you have to configure in SPRO the path is
    Purchase Order:
    SPRO> Material Management->Purchasing->/Purchase order-->Release procedure ---> Procedure with classification ---> set up procedure with classification ---> double click on Release strategies and Workflow.
    If you don't know about this configuration, you have to confirm with your MM consultant.
    Thanks and Regards,
    Prabhakar Dharmala

  • 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

  • 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 Req release strategy help

    PR's generated from MRP are being blocked, however when I convert a planned order from MRP into a PR it is automatically released. I want MRP generated Reqs to be also released. I tried creating a new class, characteristic and strategy group but ran into problems when assigning the class to the group. Basically we just want all reqs created from MRP to be released and not go through workflow. Any ideas? My inital thought was to use the creation indicator EBAN-ESTKZ with the value of B (MRP) and U (converted planned orders)

    hi Ryan
    U can use only one release class in PR release strategy
    error is because ur trying to use another class add the charactaristics ib existing class and configure release strategy
    Vishal...

  • Purchase Req Release strategy - Requestor /Approver

    We want to skip the Approver to release his own purchase requisition without workflow set up.Is it possible in ECC6.0 ?. Any help will be highly appreciated
    Thanks
    Nick

    Hi Nick
    While configurating add P group as one of charactaristic.Then maintain values of all P. Group in this charactaristic
    While defining Release strategy Do not tick against Approvers P group which means release strategy will be skiped for him
    ( Release strategy--classification here u difine value for P Group skip P group here)
    Cheers!!!
    Vishal...

Maybe you are looking for