Restriction on Creation of WBS

Hello experts,
once the WBS structure is finalised, is there any way to restrict any further creation of WBS by user status..? my business requirement is once structure is finalised, any new wbs should not be added in present structure. Is this possible by user status..?
regards,
Rahul Kulkarni

Hi Rahul,
     Use the concept of code masking for the project and there is check box (Lck) in the customizing which restricts the further creations once you check the check box.
      OPSJ and OPSK are the transactions for customizing project code masking.
      Hope this helps !!
Regards,
Punith.

Similar Messages

Restriction on no. of WBS elements creation

Hello Experts,
Is there anyway can I restrict the no. of WBS elements that can be allowed to get created below a Superior WBS element ?
Also, is there a way to restrict the no. of Orders in which a WBS can be assigned to ?
Thanks.
Bala

Hi Pal,
Thanks for your reply.. but the problem is the no. of WBS created will be in double digits and it is not fixed , it varies from proj to proj ..
is there any User exit available for this ?
Thanks
Bala

Restrict the creation of documents in the cfolders after the Bid End Date

Hi All,
The System allows the bidders to create documents in cfolders even after the Bid Submission deadline has reached, whereas the Quotation would not be submitted as the Bid Submission date is in the past. Is there any way to restrict the creation of documents in the cfolders after the Bid Submission End Date?
Waiting for your reply,
Mary

Hi Mary,
In the competitive scenario in the first screen itself there are fields for "Due date" and "Due time". Once these entries are maintained, that particular collaboration will get freezed then and no documents or bids can be submitted post that time.
I hope this will solve your query.
Regards,
Nishit Jani
Award points only if you find the information useful.

Restriction while creation of PO

Hi,
Need your suggestion in restriction for creation of Purchase Order. The requirment is Purchase Orders should get created from PR only & PO can't be created manually. Request to advise on this.
Regards,
Ranjan

HI,
Make the Purchase Requisition filed in PO as mandatory
You can do it in screen layout for po
SPRO>MM>PUR>PO>SCREEN LAYOUT
BR
Diwakar

Purchasing: Restriction of creation of PO's on the basis of buyer / user

Hi,
We are currently working on a requirement in which the business is expecting to restrict the buyers / users from creating Purchase Orders of some specific GL natural accounts.
Is there any functionality using which we can provide lock / check on this.
As the business wants to achieve this lock, since the users (buyers) are using the same responsibility and those responsibilities might have their own independent locks on the usage of Balancing Segment Values and other Cross Validation Rules.
But, we are looking for something specific which will restrict the creation of PO's based upon the login of user / buyer / PO Creator itself.
Any inputs in this regard shall be of great help.
Regards,
Saurabh Singhal.
Bangalore, India.

Pl do not post duplicates - Purchasing: Restriction of creation of PO's on the basis of buyer / user

Issue in BAPI_PS_PRECOMMIT in mass creation of WBS Elements

Hi,
I am facing a issue with BAPI_PS_PRECOMMIT.
we have the following WBS Hierarchy:
S - Proj, (level1)
S-XXX WBS Element (level2)
S-XXX-001 WBS Element (level3)
I have created a program for mass creation of WBS elements creation
which uses the following BAPI's
BAPI_PS_INITIALIZATION
BAPI_BUS2054_CREATE_MULTI
BAPI_PS_PRECOMMIT
BAPI_TRANSACTION_COMMIT
The proj: 'S' and the level2 WBS element: 'S-XXX' already exist in the system.
When I run the program for delta load, so as to create the following level3 WBS elements:
S-XXX-001
S-XXX-002
S-XXX-003
The system is throwing the following errors at the BAPI_PS_PRECOMMIT:
1. Final Check of the project definition and WBS elements: Error
2. Validation unsuccessful
Pls help me on this.
Thanks,
Deepak

Check the WBS elements doesn't exist already in your system.
Here is what I coded some days back for deletion of Network Activities, most of the things are same.
You are doing for WBS element.
* Call to initialization BAPI Before Delete
      CALL FUNCTION 'BAPI_PS_INITIALIZATION'.
* Call to Network Activity Deletion BAPI
      CALL FUNCTION 'BAPI_BUS2002_ACT_DELETE_MULTI'
        EXPORTING
          i_number           = t_bapi_activity-network
        TABLES
          it_delete_activity = l_t_del_vornr
          et_return = l_t_bapiret2.
      DELETE l_t_bapiret2 WHERE type <> 'E'.
      READ TABLE l_t_bapiret2 INDEX 1.
      IF sy-subrc EQ 0.                                      "If error in Deletion
        MOVE: f_idoc_contrl-docnum TO t_idoc_status-docnum,
              l_t_bapiret2-type TO t_idoc_status-msgty,
              'CNIF_PI' TO t_idoc_status-msgid,
              l_t_bapiret2-number TO t_idoc_status-msgno,
              l_t_bapiret2-message TO t_idoc_status-msgv1.
              MOVE c_idoc_status_error TO t_idoc_status-status.
              APPEND t_idoc_status.
              ROLLBACK WORK.
              EXIT.
      ELSE.                                                  "If Delete is successful COMMIT
* Call to PreCOMMIT BAPI
        CALL FUNCTION 'BAPI_PS_PRECOMMIT'
         TABLES
           ET_RETURN       = l_t_bapiret3.
* Call COMMIT BAPI
*        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
      ENDIF.
The other solution is use BAPI_PROJECT_MAINTAIN.

Restrict the creation of customer master records at sales area level

I know that you can supress fields at the company code and sales area level in customer master, but, is there a way in configuration to restrict the creation of a customer master record at the company code and sales area levels? Only the general data level is needed for this customer account group.
Any help would be greatly appreciated!!

Hi
Create the Customer Master without entering the Company Code and sales Area. The system will allow and ask you to fill only the General Data.
The other way is that Create a Account Group and suppress its all Fields of Accounting View and Sales Area View, so that for that account group you will have to maitain only the General view.
Regards
Amitesh Anand

Restrict PO creation from PR.

Hi all,
I have created a RFQ with reference to a PR.Can i restrict
the creation of further documents (Like PO,contract scheduling agreement)
from this PR.
Thanks,
Tess

Hi,
If you want to have requisitions that are ONLY used to generate RFQs and they should not be able to be converted into P orders of contracts. I would still consider using a release strategy, (or if you are currently not using release strategies on P reqs, you can use the non-classification release process)
The process could be as follows,
create a new P req type (called RFQ or similar).
When someone wants a requisition that can only be used for RFQs they use this document type on the requisition.
The very basic release process blocks all P reqs of document type RFQ 9or whatever you have decided to use). the release indicator used is one that is set to allow RFQ but not allow PO creation.
There is no need for these documents to ever be released and so there is no need for any further steps in the process.
So from a users point of view all that happens is that they choose the correct document type when they generate the P req and that is it, everything else works without further input. If anyone tries to create a PO or contract from an "RFQ" purchase requisition they will get the standard message saying that the requisition cannot be converted to a PO etc.. (but you can still convert it to an RFQ.)
Whatever solution you use there will have to be some user input and the above (in my opinion) keeps this to an absolute minimum(they just have to select the correct document type).
Forgive me if I have misunderstood the problem.
Steve B

Restrict PO creation for multiple plants for same company code

Hi Gurus,
We want to restrict PO creation for multiple plants in the same company code. Based on Standard SAP settings for Purchasing organization assignment with multiple Plant and multiple Plant assignment with single company code, this is happening. Is there a way that we can restrict by doing some customization change.
Any thoughts or ideas will be highly appreciating.
Thanks and Best regards,
Karun Kumar

Hi,
Said functionality is not available in SAP standard.
To avoid the same ,i can suggest implement release strategy for PO,and then higher authority / commercial team can check created PO,if multiple plants available in single po then they have the option of rejection for the same.
Or else check BADI-ME_PROCESS_PO_CUST,take the help from abapor and apply the restriction to select multiple plant in PO.
Hope this will resolve your query,
Thanks & Regards,
Sandesh Sawant

QM - restrict lot creation in I. Type(08) for S Loc to S Loc transfer

Hi All,
Thanks in advance for reply.
We have requirement for restriction in creation of Inspection Lots using inspection type u2013 08, while stock transfer from storage location to storage location only.
Inspection type 08 is used for stock transfers thourghout various plants.
But in one of the plant, there is internal stock movement from one storage location to another. During this posting system is creating inspection lot(origin 08), which is not required.
Our location is WM and HUM managed.
Please let me know how can I restrict creation if Inspection lot in above case.
Best regards,
Ravi

Hi,
Actually we need QM activate for 311 movement type.
We have two scenario in same plant & same material.
1) Storage Location to storage location transfer(HUM managed location)
2) Plant to Plant transfer(without HUM managed location)
In material let say A, I have maintain insp type 08 & in insp type details i have activated isp with HU. Hence when I do the location to location tansfer,system is creating Inspection lot for 08 with handling unit.
But when I transfer the same material from one plant to other,system is not creating lot as this transfer is not with handling unit.
For this I have created one more insp type Z1 & attach to insp lot origin 08 but still insp lot is not created while plant to plant transfer.
Pls suggest.
Thanks,
Ritesh/Ravi.

API User Hook for Restricting Category Creation in a sepcific catalog

Q: API User Hook for Restricting Category Creation in a sepcific catalog by a specific responsibility. I want to capture GO button process event?
Hi All,
Can anyone help me if anyone have used user hook for OLM? My requirement is to restrict course creation for the specific category... when we select category and select course and click on go button which process is calling? How can we identify the BP Package and Procedure name of that GO button?
urgent reply shall be a great help.
thank you.
Regards,
AD

OK, I just tried to insert an element entry from the API and it works perfectly
The problem seems to be coming from the form. Is the form not using an API?
If this is the case, should I do a personalization and run a PL/SQL procedure each time a change is made?

ME23N restrict IDOC creation and keep traffic light yellow

Hi,
I have a requirement in which I need to restrict the EDI IDOC if there are errors in the PO. Also as the IDOC is not created the messages (type NEU) should remain with the yellow traffic light as the IDOC is not processed. What would be the best approach to keep the traffic light yellow , I have identified the point to restrict IDOC creation but the traffic light is set to red.
Thanks,
Esha

Hello Esha,
I have identified the point tojavascript:; restrict IDOC creation but the traffic light is set to red.
Yellow light in Output type shows its Not Processed. If you are talking about exits EXIT_SAPLEINM_002/EXIT_SAPLEINM_011 they come into picture when Output type processing started. So ultimately they will have either Success/Error status.
Even by setting sy-msgty = 'W' in EXIT_SAPLEINM_002 and raising exception will not help.
You can play around with FMs mentioned in group WMCP and can check.

Restrict IDoc creation by using deactivate change pointers

Hi Experts,
I am trying to restrict the creation of IDOCS by deactivate the change pointers from a ztable. if the record in ztable and BDCP table match then i should deactivate the change pointer. And restrict the creation of Idocs.
pls, suggest me soon... its urgernt.......
Regards,
CHK

Maybe using program RBDCPCLR to delete change pointers you don't want to use?

Restricting BP creation

Gurus,
Could I please know how do i restrict the creation of BPs on the basis of their Post Codes? Say if I dont want to allow creation of a BP whose address lies in a particular post code and the system shows an error message saying post code not in your area.
Thanks & Regards.

Hi Dave,
Put all your checks in method EH_ONSAVE thats in controler.
for example:
   Check_Address(
          EXCEPTIONS
            save_error = 1
            OTHERS     = 2 ).
    IF sy-subrc <> 0.
      lv_msg_e = lv_msg_e + 1.
    ENDIF.
Inside the our check method put current Error handling:
DATA: lv_msgsrv TYPE REF TO cl_bsp_wd_message_service.
    lv_msgsrv = cl_bsp_wd_message_service=>get_instance( ).
    lv_msgsrv->add_message( iv_msg_type = 'E'
                                           iv_msg_id = 'ZCRM_MSG'
                                           iv_msg_number = '005'
                                           iv_msg_level = '8' ).
Good Luck
Eli Steklov
<b>Please Reward Points if it helped :-)</b>

BAPI for Production order creation against wbs element

dear all,
I am using BAPI (BAPI_PRODORD_CREATE) for Production order creation against wbs element.I am putting following input paramters in this
material no,
order type
plant
qty
basic start dt & end dt
wbs
But during GRN it is not taking the account assignment as project stock i.e. its picking movement type 101 but it should be 101Q.
For this what changes are required.
regards
ravi arora

Hi,
2 options i can think of:
1. Create a BDC program by recording co10
2. Create a planned order with order type PR using BAPI_PLANNEDORDER_CREATE, specify the WBS element & other details. Now use BAPI_PRODORD_CREATE_FROM_PLORD to create a production order with reference to the planned order created earlier.
I believe option 2 should meet your need. Check & revert.
Regards,
Vivek

Restriction on Creation of WBS

Similar Messages

Maybe you are looking for