Purchase order Doc type

Hi,
While making PO,i want to make Account assignment category to be mandatory for a particular document type.
How to do this?
Regards

hi,
Its not done for the document type...
either it can be done for the material type or from PO screen layout...
For PO its done from
SPRO --> MM --> Purchasing --> PO --> define screen layout -->? choose me21 --> Basic data, item --> make it mandatory...
SPRO --> Logistics general --> MM --> Mateirla type --> define material type --> screen layout --> check here...

Similar Messages

  • Table for combination of Purchase requestition doc type and Purchase order doc type

    Hi,
    scenario:
    Purchase requestion has document type of Direct purchase which has allowable item category "Standard, consignment, subcontracting, third party and stock transfer".
    Purchase order has document type of indirect purchase which has allowable item category "standard and services".
    Now i saw in Define Document type OMEC, 'Doc type-Direct purchase' of purchase requestion is being linked to 'Doc type-Indirect purchase' of purchase order.
    Question:
    Can you please let me know how to pull of data for combination of  'Doc type-Direct purchase' of purchase requestion and 'Doc type-Indirect purchase'  of purchase order from SE16N? (assuming that we dont know what PR is converted to PO for the above combination)
    Note: Please don't delete this thread

    You did the hardest part: finding the custo in SPRO.
    Once you there, just click "table view" :
    and then on "print"
    Once you click, you see the table name you are looking for:
    Hope it helps,
    Génia.

  • Event : changing purchase order's type in transaction ME21N

    Hi all,
    I am looking for a user exit or an enhencement to set some abap code when a purchase order's type is changed by the user in transaction ME21N.
    Thanks.
    Regards,

    Hi,
    Please find the user exit list below for ME21N. You can try out.
    USER EXIT
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    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
    LMEKO001 Extend communications structure KOMK for pricing
    LMEKO002 Extend communications structure KOMP for pricing
    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
    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
    M06B0003 Number range and document number
    M06B0002 Changes to comm. structure for purchase requisition release
    Thanks,
    Raj

  • Purchase Order Document type

    Hi
    I am trying to define new document type for Purchase Order.
    I am not able to understand the last step like link purchase requistion to document type.
    There are 2 columns Purchase Requistion =Reference Document and Purchase Requistion= Current Document.I am not able to understand the significance of this step.Can anybody let me know what is the last step for configuration
    Regards

    Hi
    It means that which item categories allowed for that  document type of PO.
    Like for document type NB allowed item categories are standard,B,K,L,S.
    And combination of purchase requision(doc type) with item category and PO(doc type).
    this combination allow you to <b>create PO against the Purchase requision</b>.If this combination of document type is not there u will not able to create PO using that PR document type
    Vishal...

  • Authorization based on plant and Purchase order document type

    Hi
    My client has a requirement wherein a user will have authorization for transactions only in his plant. But only for Purchase order document type UB (Stock Transport Order) the user should be allowed to create for all plants.
    In short, if Purchase order document type is UB, should be allowed for all plants
                 if Purchase order document type is NB, should be allowed to only one particular plant.
    My Basis person says that such a restriction is not possible.
    Kindly suggest me on how to provide a solution to this.
    Thank U.

    Hi,
    This is possible.In this case you need to create two seperate roles.
    1)Create purchase order for all plants (This can be used in long text)
    2)Create purchase order for <plant no> plants.
    For case 1:--
    i)Populate field BSART of M_BEST_BSA with UB.
    ii)Populate field WERKS of M_BEST_WRK with '*'. SAP reccomends to fill up organizational data through organizational level tab only.So while doing this step you need to put * from organizational level tab only.
    For case 2:--
    i)Populate field BSART of M_BEST_BSA with NB.
    ii)Populate field WERKS of M_BEST_WRK with 'plant no'.
    Dont worry about the objects i mentioned those are maintained through SU24 and will be automatically pulled once you insert ME21 transaction code.
    Let me know if it helps.
    Thanks,
    Aveek

  • Purchase Order Document Type and Account Assignment

    Hi  ,
    We have a requirement to control Account Assignment in Purchase Order Item line based on the Document type selected on the Purchase Order header.
    Like if user selects Purchase Order document type "ZNB" (Customized created) , then he will only able to select "K" or Blank or "P" as account assignment and similary we want to limit other Account assignments based on the Purchase Document type.
    How can we make this Control settings?
    Regards
    Shrey

    Hi,
    You can't really limit the account assignment categories per document type, at least not directly.
    You can limit the item categories that can be used for a document type via configuration:
    Materials Management > Purchasing > Purchase Order > Define Document Types
    Within this transaction you can define which item categories are valid for a specific document type.
    You can then define which account assignment categories are valid for each item category
    Materials Management > Purchasing > Account Assignment > Define Combination of Item Categories/Account Assignment Categories
    BUT
    limiting the account assignment categories that are valid for an item category will affect ALL purchase order document types that this item category is valid for. And you can't create your own item categories as this is a SAP standard table that can NOT be altered.
    Regards,
    Monika

  • Remove Planned Purchase Order from Type field on Purchase Order form.

    Have requirement to remove Planned Purchase Order from LOV on purchase order form in 11.5.10.2. Tried to disable the Planned Purchase Order document type but Disable field isn't updatable. How can I remove Planned Purchase Order from LOV?

    You can modify list of values in a form with CUSTOM.pll.

  • Purchase Order Service Type

    Hello All,
    My client wants the gross price to be calculated based on the quantity on purchase order (service Type).
    Can anyone help on this please.
    Cheers

    Hi Satish....
    You can see the Gross Price Calculations on Right Click Gross Profit Option for Service Type.....
    Please check it on Sales Window....
    Regards,
    Rahul

  • Purchase order service type through code

    Hi Experts,
    Can we create a purchase order of type service through code ?
    Please give me some sample codes
    Thanks in advance
    Regards
    Arun

    Hello,
    I think this is an userfield? Or a field that i don't know?
    purchaseOrder.Lines.LocationCode = 2
    For testing you must keep your code simple, first only fill the mandatory fields:
    And catch you errormessage as well.
    Dim purchaseOrder As SAPbobsCOM.Documents = B1Connections.diCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInvoices)
                'Set values to the fields
                purchaseOrder.DocObjectCode = BoObjectTypes.oPurchaseOrders
                purchaseOrder.CardCode = "V0001"
                purchaseOrder.DocType = BoDocumentTypes.dDocument_Service
                purchaseOrder.DocDate = Today
                 purchaseOrder.DocDueDate = Today
                purchaseOrder.TaxDate = Today
                purchaseOrder.Lines.ItemDescription = "TESTPO"
                purchaseOrder.Lines.AccountCode = "500201"
                Dim lRetCode As Integer
                lRetCode = purchaseOrder.Add
                If lRetCode != 0 Then
                    B1Connections.theAppl.SetStatusBarMessage("Error occured.", SAPbouiCOM.BoMessageTime.bmt_Short, True)
                Else
                    B1Connections.theAppl.SetStatusBarMessage("Purchase order created.", SAPbouiCOM.BoMessageTime.bmt_Short, True)
                End If
    HTH Regards Teun
    Edited by: Teun Aben on Oct 22, 2010 3:54 PM

  • What is the purpose of using rush order  doc type?

    what is the purpose of using rush order  doc type?

    hi,
    In a rush order transaction, the customer picks up the goods or you deliver the goods on the same day as the order is placed. In the standard system, when you save this sales document type, a delivery is automatically created and billing is related to the delivery.
    In the standard system, sales document type SO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted.
    Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.
    CHAN

  • Purchase Order Document type FO?

    Hi,
    Why we need to use in Purchase Order Document type FO?
    With Document type NB also we can make Services ,Right?
    Thanks

    Hi
    FO - Frame work order Document type is a standard document type , which is used for Blanket Purchases, Purchase of services.
    The FO document type has a Validity Start & End date feature whcih is not in the NB document type(You can get the same in NB also after cusotmization)
    Services & limits are also presnet. The FO document type is limited to usage for Iterm categories
         Standard
    B     Limit
    D     Service
    All these can be made for NB also, but only after customizing.
    Thanks & Regards
    Kishore

  • Purchase Order Document Type Defaulting in ME58 while converitn PR to PO

    Dear All
    While converting Purcahse Requesition to Purchase Order in ME58, System defaults one Purchase order document type . Ofcourse we can overwrite that
    But would like to know how this defaulting can be controlled in SAP
    Regards
    Shyam

    Hi,
    If you have maintained an "Order Type" in table T160 (customizing
    transaction OMH5) for the entry "ME21", then this value will be
    defaulted in the pop-up in transaction ME58. Otherwise, the "Order Type"
    of the Requisition will be defaulted.
    The following code block of program (Note 125969) is for your reference:
    SELECT SINGLE * FROM T160 WHERE TCODE EQ SY-TCODE.
    IF SY-SUBRC EQ 0 AND NOT T160-BSART IS INITIAL.
       RM06E-BSART = T160-BSART.
    ELSE.
       SELECT SINGLE * FROM T160 WHERE TCODE EQ 'ME21'.
       IF SY-SUBRC EQ 0 AND NOT T160-BSART IS INITIAL.
         RM06E-BSART = T160-BSART.
       ELSE.
         RM06E-BSART = BAT-BSART.
       ENDIF.
    ENDIF
    According to the code above, the system first checks the table T160 for
    ME58, if there is no data then for ME21, if there is no data, then it
    defaults from PREQ.This is the same as described in the note 114213.
    BR
    Nadia Orlandi

  • I need output type NEU automaticaly for create purchase order document type

    Dear Experts,
    I need output type NEU automaticaly for create purchase order document type NB
    when transaction code MN04, I am doing the following:
    (1) I selected the third option Purchasing Output determination: Document type
    (2) I selected the output type NEU.
    (3) In condition records in document type , i have chosen NB.
    (4) In name its automatically coming as Purchase requisition
    Please suggest how Purchase Order NB will come

    Hi,
    Check & press F4, NB Purchase Order (for catagory F) will be there after entering PO output type NEU & then maintaion the condition record in MN04.
    Output type NEU automaticaly defaulted during purchase order creation with document type ,then just fine tune the output (message) type in following path:
    SPRO--->MM->Purchasing>Message>Output control->Message types> Define message type for Purchase Order----->Fine-Tuned Control: Purchase Order
    Now here select the check box corresponding to your output(message) type NEU to have print output automatically displayed & save.
    Now try to creating Purchase Order & you will have default message type NEU.
    Regards,
    Biju K

  • Material Statuses based on the Purchase order Document type

    Hi Experts,
    We need to maintain the Plant material status based on the purchase order document type.
    Example - If I am using NB for normal purchase orders and ZB for STO procurement then, there should be a material status which should give warning message - 'do not use ' for ZB STO purchase orders and it should allow to create NB purchase orders for that same materials.
    Please advise what are the possibilities?
    Thanks
    Regards
    MM

    Hi Gurus,
    Thank you for  your reply, Please find my replies below
    @@ - Mallinath - We need this restrictions for some type of materials ( with specific Material types) which should not be procured through inter company STO process, buying plant should use the normal purchase. for other Material types they should be able to use the inter company STO process.
    @@ DEV - We are already using the Spl. Procurement keys for inter company STO process.
    Example - Material type ZXYX should not use the inter company STO process, but it should be allowed all other processes.
    Please advise how we can control this process?
    Thanks
    Regards
    Raja

  • Restrict purchase order document type at plant level

    Dear,
    I would like to restrict the purchase order document type at plant level,
    Plz help me.

    Hi Dear,
                 at the Plant level you have to use the below given Authorization Objects for the Users in different Plant
    M_BEST_BSA     Document Type in Purchase Order
    M_BEST_WRK     Plant in Purchase Order
    Give the values of the respective Plant and Order Type for the Respective Users.
    For more help you can contact your Security Team.
    but before that please check out in the T-Code SU24, if both the Objects are active, if not then ask the ABAP person to activate them.
    Hope it helps you.
    regards,
    yawar Khan

Maybe you are looking for