Restriction on PO creation

How to allow users  to create P.O only for one material type and cost centre related P.O.

Hi
perticulat material type object assign with the users. so, that users only allow with that material type and document type.
take the help of Basis people. this is purly authorization contraol.
Laxman

Similar Messages

  • How to restrict Duplicate Customer Creation in SAP

    Dear all,
    How can we restrict duplicate customer creation in SAP SD.
    We are into retail sector, across the store customers are being created by different employees.
    in this way for many customers more than one business partner records are being created.
    we are looking for a sytem wise functionality to restrict the customer master creation (for Sold to party only) if name1, telephone number and street field values are same, then system has to stop customer creation by giving an error message.
    Is there any standard functionality to address these requirement. If so how could we configure it.
    Any of you can help us to solve the issue. your solutions and help will be highly appreciated.
    thank you.
    Raghu ram.
    Edited by: Raghu Ram on May 26, 2008 5:34 PM

    Hi,
    2 solutions :
    - Procedure manually (no SAP) ;
    - Use extension SAP (SMOD : SAPMF02D) to check with differents data before recording.
    No solution in standard.
    Regards,
    Lionel

  • Restriction of RFQ creation without PR reference

    Dear all,
    I want to restrict the RFQ creation without PR reference for certain document type in RFQ say AN.How to do that???
    Regards,
    Atanu

    Hi,
    Creation of RFQ without any reference is standard functionality. So restricting it without reference of PR is quite tricky.
    I can suggest you to use field selection key.
    For example, as standard for document type AN, SAP uses field selection key ANA. You copy this key and create your own new key. In this key you can find field 'PR' under field selection group 'Reference data. item'. Mark this field as required entry. Assign your new key to document type.
    Please try this out and let me know how it worked.
    Regards,
    Sameer

  • Problem with restriction of material creation

    I have a problem  regarding this code logic mention below
    itz for checking the plant and profit center should be same . restrict by a message at the time of material creation .
    now when we create a Alfanumeric plant and the profit center and we enter the same this message is stil comming and itz restrict the material creation .
    can anybody please help me out for change the logic of this code .
    break-point.
    3       CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
    4         EXPORTING
    5           input         = MARC-PRCTR
    6        IMPORTING
    7          OUTPUT        = MARC-PRCTR
    8                 .
    9     *break-point.
    10       if sy-tcode eq 'MM01' or sy-tcode eq 'MM02'.
    11       if RMMG1-WERKS <> MARC-PRCTR and MARC-PRCTR is not initial.
    12       message id 'ZS' type 'S' number 057.
    13       endif.
    14       endif.
    15       IF ( sy-dynnr(1) = '4' OR sy-dynnr = '0060' )             "note 754457
    16          AND NOT c_set IS INITIAL AND
    17           ( x_win NE sy-srows OR y_win NE sy-scols )
    18           and ok-code is initial and c_classification IS INITIAL.
    19         bildflag = x.
    20       ENDIF.

    Hi,
    Aren't you missing an = in the following line...
    11 if RMMG1-WERKS MARC-PRCTR and MARC-PRCTR is not initial.
    Shouldn't it read as follows?
    11 if RMMG1-WERKS = MARC-PRCTR and MARC-PRCTR is not initial.
    Regards,  Andy

  • How to restrict inbound delivery creation by incomplete log

    Guru's
    I have a requirement of not to create an Inbound delivery if the filed in the "means of trans id " in the delivery header is 'BLANK".If i create an incomplete log for the field LIKP-TRAID (Warning message enabled) for Delivery header in transcation OVA2 .Now if i create an inbound delivery  with "means of trans id " BLANK .It is giving only warning message it is not stopping me from creating an Inbound delivery .
    Can you please let me know whether we can restrict creation of inbound delivery.
    Thanks

    Try through user exit,If system does not find the means of trans id then syem stops to crete inbound delivery.Chcek this user exit V50Q0001 with your ABAPer it may help you.

  • Restrict Info Record Creation Based on Material Type

    Dear colleagues
    I would like restrict material info record (ME11) creation based on given materialsu2019 material type (MARA u2013 MTART). Is it possible such control? If yes, can you please provide the way?
    Best regards

    Dear AP,
    Unfortunately I wasnu2019t able to find any user exit, badi or etc. That's way I need to post the question to the forum. Before providing any answer please consider that no question is post without any research and give the audience specific, to the point answers not such irrelevant ones.
    Thank you

  • Is it possible to restrict the object creation for stateless session beans

    Hi,
    Is it possible to restrict/fix the ejb object creation for stateless session beans in application server?
    For example, i want to configure the application server ( am using JBOSS ) to create maximum of 10 session bean objects. and if any requests for the stateless session bean come, as application server has created 10 objects, the requests should be blocked.
    Thanks in advance,
    nvseenu

    You can keep a counter in the application code. A static var won't work, but an entity and a consistent id should. This version would affect performance, but it would be portable to other app servers.
    // ConstrainedBean.java
    package unq.ejb;
    import javax.ejb.Stateless;
    import javax.ejb.CreateException;
    import javax.annotation.PostConstruct;
    import javax.annotation.PreDestroy;
    import javax.persistence.PersistenceContext;
    import javax.persistence.EntityManager;
    @Stateless
    public class ConstrainedBean implements Constrained {
        final static int DEFAULT_COUNTERID = 1;
        @PersistenceContext EntityManager em;
        @PostConstruct
        protected void init() throws CreateException {
         ConstrainedBeanCounter counter =
             em.find(ConstrainedBeanCounter.class, DEFAULT_COUNTERID);
         if( counter == null ) {
             counter = new ConstrainedBeanCounter();
             counter.counterId = 1;
             counter.counterValue = 0;
             em.persist(counter);
         if( counter.atMaximum() ) {
             throw new CreateException("error attempting to create > 10 beans");
         else {
             counter.increment();
        @PreDestroy
        protected void destroy() {
         ConstrainedBeanCounter counter = em.find(ConstrainedBeanCounter.class,
                                   DEFAULT_COUNTERID);
         counter.decrement();
        public void doSomething() { System.out.println("doSomething()"); }
    // ConstrainedBeanCounter.java
    package unq.ejb;
    import javax.persistence.Entity;
    import javax.persistence.Id;
    @Entity
    public class ConstrainedBeanCounter implements java.io.Serializable
        @Id public int counterId;
        public int counterValue = 0;
        public void increment() {
         counterValue++;
        public void decrement() {
         counterValue--;
        public boolean atMaximum() {
         return counterValue > 9;
    }

  • Restriction in PO creation

    Hi,
    Need suggestion for one business requirement.
    How to make PO creation only for PR total value above 10000 LE on the other side If the PO value is less than 10000 LE , no need to have a PR as a reference to create PO.

    You have to use an exit or a Badi to control your requirements, there is no customizing setting for this.
    While the requirement for a requisition is almost understandable, restricting  PR creation  in case the value is less than X  is not understandable, as it just causes double processes, because the info that something has to be ordered needs to be transmitted somehow from the requisitioner to the buyer.
    A further question is: what is so important in the requisition to make it mandatory?
    A buyer can be controlled with a release strategy on the PO.
    And you must not forget that there is not necessarily a 1:1 relation between PR and PO.
    what if 2 persons wants independent of each other an item with a value of 6000, and the buyer put it together into 1 PO, so he finally has a PO of 12000. Does he then need to ask both to give him a PR? Or will he better create 2 POs to get around this restriction?
    We have for example the email address of the requester in the PR,  when the invoice is received and the quantity has a difference then it get mailed to the requester for approval. Without PR we could not do this process, hence it is easy - no PO without PR, just 1 process.
    Think about if it makes really sense to restrict people from creating PR if the value is less than x.

  • Restricting Sales Order Creation for Customers with specific AccountGroup

    Hi
    We have 2 Accont Groups for Customers namely Actual & Prospective.
    We wish to allow Enquiry / Quotation and Order creation for customers with Account Group ACTUAL and wish to allow only Enquiry and Quotation creation for customers with Account Group as Prospective.Is there anyway i can apply Sales Order creation block on an ACCOUNT GROUP on whole and not on Individual customers...
    Regards
    Sanjeev Bagaria

    Hello
    I did this through Listing Inclusion / Exclusion.
    (1) We created a new Customer Group 99 for Prospective Customer
    (2) We then created a new Condition table xxx with Customer Group & Material Type(as footer)
    (3) We then created this new Access Sequence Customer Group / Material Type to Exclusion Procedure B00001
    (4) We then assign the Exclusion Type B00001 to Sales Documents ZDOM & ZEOR our Order Sales Documetn Types
    (5) And finally we created a record for Exclusion with 99 Customer Group and Material Type as FERT..
    This now restricts creation of Sales Orders for all my Prospective Customers provided Customer Group is maintained in Customer Master. We are now also able to make Enquiry / Quotation and Sample Sales Order for Prospective Customers sicne we have Different Sales Document Types for all these and have assigned Exclusion only to normal Sales Order Document Type.
    Thanks a lot for all the suggestions provided.
    Regards
    Sanjeev

  • How to restrict users from creation of varients in report transaction

    Hi All,
    I have a requirement where buisness wants to restrict users in creating varients in report transactions.because of create options users will be creating more screen varients which will be disturbing for the other users to select a particular standard varient.Kindly give ur input regarding this
    With regards
    Girish A

    Hi,
    First edit the role assigned to users using PFCG.
    Then go to Authorization tab and click on "Change Authorization Data".
    It will opened up the profile of the role. now find the authorization object "S_PROGRAM".
    In that edit "User action ABAP/4 program" object.
    Remove "VARIANT" check box if it was checked and save. Now press
    Generate button or "Shift+F5".
    That's it.
    You can ask for this to your basis team. They can perform this task  easily.

  • How to restrict the idoc creation based on the distribution model

    Hi all,
    I want to create the idocs for certain material types only, for this i configured Distribution  model and set the filter for material types.
    If the delivery is created with the material type which is not in the filter means,
    Idoc is creating for that Delivery with header segments only and restricting Item level segments.
    it is coming to XI and failing in mapping every time.
    I do not want to generate the whole idoc itself. Am i missing any thing??
    Regards
    Edited by: Suman gupta on Jun 10, 2010 11:13 PM

    Hi Mike,
    >>config in PI in the routing condition - if no lines exits don't send the message to the mapping/receiver
    If no lines exists we can restrict don't send to receiver, but how can we restrict dont send to mapping??
    It comes to mapping and failing in PI MONI.
    Is there any way that i can restrict the Idoc generation itself in ECC ??
    Regards

  • How to restrict production order creation for the WBS

    Dear Gurus,
    Our client is is using PS & PP. So that as per current procedure material required for the particular project will be uploaded into the CJ20N i.e. it will be assigned to the network.
    So that on that basis production orders will be created with the transaction co10. But in this case there is no linking between the orders created & quantity required in the project.
    So is there any restriction that by using co10 we will be able to create the production order for the material which is enterd in to the wbs with not exceeding the quantity also.
    With Regards...
    Abhay

    Dear Abhi,
    But why do you require to create produciton order manually through co10?
    Any how you must running MRP in MD51 where in you will get your planned orders which you can convert to production orders!
    Thanks.

  • Restrict Sales Order Creation for Serial Numbers already in Sles Order/Sold

    We have recently implemented variant configuration and usage of serial numbers.
    Facing some problems because of this.
    1. If a Material is in Stock e.g Material xyz and serial number 123
    System allows us to create sales order and Deliver and Invoice Serial number 124.
    I have activated Indicator: Serial Number Existence Requirement thru OIS2. However it solves only part of my problem.
    If for Material xyz serial number 123 is in stock but serial number 124 has also been created and assigned to material xyz but not in stock, then system allows me to create sales order, delivery and billing for material xyz and serial number 124.
    When I check MMBE I see zero stock when I click on serial number I see serial 123, which is inconsistent.
    How to ensure that such a situation does not happen?
    Also I do not want the system to create a sales order for a material for which sales order has been created.
    e.g. for material xyz and serial 1234 if sales order exists then system should not allow creation of another sales order for the same combination.
    However in case of consignment orders the system should allow only the logical transactions like consignment fill up or consignment returns.
    Please help.
    Regards
    Rajkumar Reddy

    Hi
    This is nothing but Creating Roles  and assigning the respective authorizations to the Roles  for giving the access to the related Tcodes
    This has to be done by basis people
    using the Transactions
    PFCG
    SU21
    SUIM
    such that every user can not create the sales order or change it.
    Reward points if useful
    Regards
    Anji

  • How to restrict/disable passcode creation

    I am hoping someone can help me with this. We have been deploying iPads in a restaurant and some customers have been going into Settings and then creating a passcode. Once this is done we have to reatore the iPad for further use.
    I have used iPhone Configuration Utility to create a configuration profile. I don't see a way in restrictions to keep a user from creating a passcode. Ideally I would like to lock the user completely out of the Settings app.
    Any suggestions would be greatly appreciated.

    Sorry but you can't prevent a user from creating a passcode. All you can do is set a passcode yourself so that someone else can't set one you don't know about. There is no way to keep any user out of the Settings completely, either. The only way to achive any of this is to use a case/mount that prevents access to the Home button, then for iOS 5 systems turn off the multitouch gestures.
    Regards.

  • RESTRICT PURACHSE ORDER CREATION IF INFO RECORD IS NOT MAINTAIN

    HI,
    I WANT TO RESTRICT THE USER FROM CREATING PURCHASE ORDER (ME21) IF HE HAS NOT UPDATED THE INFO RECORD FOR THE SAME.
    I WOULD LIKE TO KNOW WHAT ARE THE FIELDS EFFECTED FROM WHICH TABLE AND HOW TO DO IT.
    WHAT I KNOW IS INFO RECORD (ME11) AFFECTS EINA TABLE, BUT HOW TO RELATE THIS WITH P.O .
    PLEASE HELP ME.
    THANKS.

    Thanks

  • Restriction of order creation

    hi all,
    we are working of Ps-PP scenarion.
    orders are created w r t wbs element. in our company by mistakely users created two orders for a assembly for the same wbs element. one by converting plann order to production and another one with CO10 tcode.
    i want to restric this duplication orders creation pls help.
    thanks in advance.

    Dear
    If you do not want to create order refernce to WBS directly , then  put a authorisation control with the help of your Basis team for SAP Txn -CO10 because you may be running MRP on WBS and geneated Planned order refernce to WBS and conver them to PO.
    Otherwise you can goto CMOD and put a screen variant at User level for CO10 specfic to user
    http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation
    Regards
    JH

Maybe you are looking for