WBS element mandatory in PO

Hi,
At the time of creating Purch.Order (ME21N), I wanted to make WBS element mandatory when taking Account Assignment category as P(Project).
What type of customisation do I need to carry out this.
Regards,
Goraksh.

Dear,
Enter OME9 t-code.
Select account assignment category P.
Then change field status as mandatory entry of field name Project .
Then check purchase order.
Regards,
Mahesh Wagh

Similar Messages

  • To Make WBS element Mandatory for a particular Document type- Contract

    Hi ,
    I have a requiment where I have to make to Make WBS element Mandatory for a particular Document type of Contract . I don't want to use any User exits or Badis for this .
    Please let me know if there is any configuration that can be done to achieve this .
    Regards,
    Hari.

    Hi ,
    It is already made mandatory in account assignment categories  but My requirment is that it should be mandatory for only one particular document type . In the account assignment categories , there is no where we can specify the document type . It is only at account assignment category level but not at document type level .
    Regards,
    Hari.

  • WBS as mandatory

    Hi,
    I want to make WBS Element mandatory at line item level in sale order.
    whats the procedure?
    Regards,
    Shruti.

    Hi Shruti,
    Firstly check in the VOV7 T.code for your Item category what is the procedure assigned to.
    suppose "20" is the procedure assigned to it.
    Goto "OVA2" T.code and select groups as "B(Sales-Item)".As the WBS element is available at the item level.
    Click on the procedures.
    Select "20".
    Click on the Fields.
    Click on new entries.
    Add table as "VBAP".
    Select the field as "PS_PSP_PNR".Select the screen as "PKNT".Select the status as "04".
    If you click on the tick mark of warning then you will receive a warning message.
    Save.
    Regards,
    Krishna.

  • WBS element field mandatory for specific sales order

    Hi Friends,
    I want to make the WBS element field in sale order line item to be mandatory for a specific sales order type. I am not able to add this field in incompletion log also. So can anyone let me know the solution for this.
    Ratna

    Hi,
    As solution suggest above is correct use VBAP table and Field is PS_PSP_PNR into ur incompletion log and assign this procedure to ur Item category. And If u want to WBS element check at header level the use VBAK table and field PS_PSP_PNR and assign this incompletion log to ur sales document type.
    Once more setting is required to stop the order from saving if incompletion check is unsucessful, for that you need to check a checkbox named "Incomplete. Message" in VOV8 tcode, for ur perticular sales document types.
    Hope this will resolve ur problem.
    rgds
    Dhiraj

  • Down payment  request concept, Network or WBS element is mandatory?

    Dear All,
    To use down payment  request concept, Network or WBS element is mandatory? And without milestone billing can't use down payment?
    Regards,
    Srikanthraj

    dear
    it is not mandatory to have the Network or WBS for the billing plan .
    we will use Billing plan manually in the sales order with relevent Billing rule 4 /5 for milestone.
    regards

  • How to make WBS element field in Notification a mandatory.

    How to make WBS element field in Notification a mandatory.
    Should I use USer Exit.
    In cutomization I didnt find ant standard customization

    Hi,
         If it is about WBS element field in Maintenance Order then check up user exit ;- IWO10009 PM Order: Customer Check for 'Save' Event
    For Notification i am not sure whether this field is ther , but anything u can perform checkings via 
    QQMA0014 QM/PM/SM: Checks before saving a notification
    Alternatively u can also explore via Transaction variant SHD0 ..
    regards
    pushpa

  • How to make mandatory(usr01) field for level 1 wbs elements only from CJ20N

    Dear All,
    I have made mandatory for "PRPS-USR01" field from CJ20N transaction
    by using field exit. But mandatory field (usr01) is working for all wbs elements. I want to make this usr01 field mandatory for  LEVEL 1(prps-stufe), WBS ELEMENTS(prps-posid) only. Not for level 2 and level 3 wbs elements. Please let me know how to fix it.
    urgent.
    Regards,
    Karthik.

    You could envisage the use of validation rules in PS.
    Transaction OPSI or SPRO
    Create a validation with a message ID (Z)
    Create a step
    - prerequisite : PRPS-STUFE = '001'
    - Check : PRPS-USR01 <> ' '
    affect a message number
    Regards.

  • Making Settlement rule mandatory for creating any WBS element

    Hello All,
    We have an requirement that system should not allow us to save any WBS element until the settlement rule is maintained.
    This we want only for WBS elements where Investment rule is not assigned.
    Can alyone help me to find out if this is possible, if yes then how.
    Points Assured.
    Thanks & Regards,
    Jatinder Bansal

    Hi,
       The only way it seems possible is using exists in validations.
    if not try to check the status of the wbs element in a validation. function module is STATUS_CHECK. and i think the system might set a special status, if a settlement rule has been maintained for a wbs element.
    Rgds
    Sudhir Reddy

  • Settlement of order -WBS Element

    Dear Experts,
    Can any one tell me what is meant by WBS element and in what scenario,PM orders settlement rule created with category as WBS.If possible tell me with any practical example.
    regards
    KRISHNAN

    Dear,
    Dear,
    Budget: Amount of resources allocated under a particular head in a financial year.
    Budget Control: Having/ creating a control on the resources allocated in a financial year.
    Original Budget: The initial budget that you have allocated to a WBS element.
    Supplement of Budget: One time/ discrete increment in the original budget.
    Return of Budget: Taking out the unutilized portion of the budget.
    Transfer of Budget: Transferring the budget among two or more expense heads.
    Project Definition: A framework for a business undertaking with a fixed goal to achieve with given resources.
    The project definition contains dates and organizational information that are binding for the entire project.
    WBS Element: Individual structural element in a work breakdown structure (WBS) representing the hierarchical organization of an R/3 project. Describes either a concrete task or a partial one that can be further subdivided.
    Proposed Business Process
    Assume there are seven expense heads in maintenance department. There may be addition of expense head in near future.
    Based on the maintenance heads, maintenance department will create a project in project system. This project will be used for ‘statistical purpose’ only & will not have any financial implication.
    Upon creation of a project, WBS elements will be created as per the expense heads. So for each expense head, there will be one top level WBS element. Again these WBS elements will be divided in twelve WBS elements. These twelve WBS elements represent twelve calendar months.
    Budget will be allocated to each WBS element & the WBS element will be released from the project.
    Maintenance department will create maintenance orders as per their work requirements. These orders will be settled to cost centre, which is maintained in the settlement rule. Also WBS element will have to be mentioned in each order so that the budget control can take place. So as to capture cost from each maintenance order, the WBS element field will be made ‘mandatory field’ in maintenance order.
    So when a maintenance order is released, system will do a budget check against the WBS element mentioned. If the budget check status is OK, order is released or else it will stopped from release. If the order is stopped from release, maintenance department will have to supplement the budget. Upon supplementing, the order is released again & the maintenance cost such as, labour, material costs can be booked on the order. Again the order cost is settled to cost centre & at the same time, budget is consumed from the respective WBS element.
    Every year, maintenance department will copy the previous year’s project so as to save time & efforts to create project & WBS elements. And the maintenance department will assign the budget allocated to each WBS element in a financial year.
    It is also possible to return the unutilised budget or, transfer of budget from one WBS element to another.
    Create a project CJ20N
    Create WBS element CJ20N
    Assign Budget to WBS elementsKO22
    Display assigned Budget KO23
    Supplement Budget KO24
    Display Supplement budget KO25
    Return Budget KO26
    Display Return budget KO27
    Transfer of budget CJ34
    Hope u wull get ur answer
    Regards
    Rakesh

  • WBS element determination in SD billing

    Hi All,
    We are using WBS element for positing accounting document in billing.
    In our case flow starts from Service order->QT -> debit memo req-> Debit memo.
    WBS element is mandatory field in Service order(IW31) and with reference to Service order DMR is created.
    While creating the Debit memo in VF01 different WBS element is getting determined which is not activated for account postiing in CJ03.
    Kindly help me out why the different WBS element is coming in billing doc and how this determation will happen in billing.
    Regards,
    Shameel

    Hi Shameel,
    how are you assigning WBS element in Service Order, is it from the project or just randomly you are assigning ?
    try to find if any substitution rule assigned to the WBS in CJ20N transaction
    Also why you need Account assignment posting to WBS as Debit memo request is created with Service Order, you can settle to the Service order
    Let me know what you are trying to do
    thanks
    santosh

  • Can  WBS element be adopted as splitting characteristic for general GL

    Hello :
    In our PS module implementation, the client requires that WBS element be picked up in the line item of account payable (vendor)  during logistic invoice verification.  Currently, we managed to post below document:
       Dr:    GR/IR   -  WBS1
                GR/IR  -   WBS2
                VAT
          Cr:  Account payable (vendor)
    I am wondering whether WBS element can be selected as splitting characteristic for general GL? Therefore, WBS element can be posted for account payable.
    As fas as I know, in IMG only three characteristics: Segment, profit center and business area are preferred as   splitting characteristic for general GL.  WBS element is regarded as splitting characteristic for Controlling.
    Does anybody has experience on using  WBS element as  splitting characteristic for general GL?
    Cheers

    Hello,
    You can add PS_PSP_PNR to the ledger scenarios with the transaction FAGL_GINS which intends to be used for updating the open item and sum tables of the New GL. after that PS_PSP_PNR can be defined as splitting criteria for controlling, but  can not be defined as splitting criteria  for general ledger.
    The reason for this is that it cannot be guaranteed that such fields as PS_PSP_PNR are supplied with values on the account receivables/payables by the standard FI and integration processes. The settings as
    zero balance or mandatory field can lead to errors in the system. Therefore we do not recommend the usage of such fields as split criteria for the general ledger.
    While PS_PSP_PNR can be defined as split criteria for controlling, so the relevant lines are splitted on the Profit & Loss accounts which are relevant for the CO account assignments.
    With Best Regards,
    Gladys

  • Error Individual check for creating the object WBS Element required

    Hi Expert,
    I've a requirement to create WBS elements using BAPI. And I am using BAPIs in the following manner.
    CALL FUNCTION 'BAPI_PS_INITIALIZATION'
    CALL FUNCTION 'BAPI_BUS2054_CREATE_MULTI'
    EXPORTING
    i_project_definition = g_pdwbs
    TABLES
    it_wbs_element = it_wbs_element
    et_return = it_return
    EXTENSIONIN =
    EXTENSIONOUT =
    CALL FUNCTION 'BAPI_PS_PRECOMMIT'
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    When I do so I am getting the below errors. Please suggest.
    "Individual check for creating the object WBS Element C-497082 required ".
    "Individual check for creating the object WBS Element C-497082-0001 required".
    Please suggest how to correct this error.

    Hi Karthikeya,
    I think the project profile which you are using has a different mask and the WBS element you are passing is different to the BAPI.
    Are you able to create manually from CJ01 using the same WBS element?
    Create a project manually and it will give the list of the mandatory fields set in the config. Using that list populate the BAPI struture accordingly.
    Hope this helps.
    Thanks
    Lakshman.

  • How to delete/close WBS elements

    Hello Guys,
    We are facing following issues - We have some WBS elements that has not been migrated from company code XX (now incative). Now we canot close those WBS and we are getting errors when posting Settlements (CJ8G/CJ88).
    Error - Asset under construction not completely credited.
    There are some old bookings on the WBS (total sum = 0)  but SAP does not allow us to close it. As this is already closed company code we cannot create assets here anymore.
    Do you know if there is a way to close or delete such WBS elements?
    Thank you..

    Hi Tushar,
    Following the screenshot sent by Tomas, there are many steps which needs to be carried out before setting the deletion flag for the WBS element. One is to ensure that the mandatory fields for the asset are filled as rightly pointed out, second is to ensure deactivating the asset, third is to delete the existing PO's/PR's associated with the project. This will ensure that the WBS element is back in its original state which will then allow us to mark the deletion flag or set the WBS element as deleted. However cant we close the WBS element and then try to set the deletion flag? Is this a wrong practice you feel?
    Kindly advise
    Regards
    Varun

  • WBS Element Creation Using BAPI

    Friends,
    While creating the WBS element using the bapi,
    BAPI_BUS2054_CREATE_MULTI   I'm getting an error in Return parameter of bapi.the error is
    "Individual check for creating the object WBS Element CRA.011 required"
    FYI: CRA.011 is nothing but the WBS element which i'm trying to create.
    Pls help me in this. Advise me what are the mandatory fields to be passed in the it_wbs_element table of bapi.
    Thanks.

    Hi Karthikeya,
    I think the project profile which you are using has a different mask and the WBS element you are passing is different to the BAPI.
    Are you able to create manually from CJ01 using the same WBS element?
    Create a project manually and it will give the list of the mandatory fields set in the config. Using that list populate the BAPI struture accordingly.
    Hope this helps.
    Thanks
    Lakshman.

  • WBS element in VA01

    Hi,
    I want to make WBS element as required field in VA01 transaction.
    I tried in SHD0, but i could't make it required.
    Could anyone tell me the what transaction variant I have to choose.
    Regards,
    Chandra

    In the document type, check the checkbox Incomplete.messages. But this will apply for not only one field but all incomplete items.
    Even with SHD0 also it should be possible to make the field as mandatory. As a last resort you can use exit in MV45AFZZ for changing the screen field to mandatory.
    Regards,
    GSL.

Maybe you are looking for